What should I focus on for an Agile and Scrum interview?
Which basics should I be able to explain?
Agile fundamentals came up in 27 of 81 interviews. The most asked question compared Agile and Waterfall, appearing in 9 of 81 interviews. Start here: can you explain how the methods differ, not just name them?
- Can you compare Agile and Waterfall in how teams work, who does what, and how development moves forward?
- Can you explain how Scrum and Kanban differ in team roles, workflow, and delivery?
- Can you describe how Agile fits into software development and explain its principles and benefits?
What should I know about Scrum events and roles?
Scrum roles and events appeared in 20 of 81 interviews. Check that you can explain what happens at each event, rather than only list the names.
- Can you describe team responsibilities during a sprint?
- Can you explain daily stand-ups, reviews, and retrospectives?
- Can you describe how your team organizes its work around these events?
Can I explain how a request becomes planned work?
The questions cover the path from a stakeholder request to a user story, a backlog, and sprint planning. Check whether you can talk through that path and explain the choices you make.
- Can you turn a stakeholder request into a user story that is ready for development, with clear acceptance criteria?
- Can you explain how you split an epic and how a story differs from a task or use case?
- Can you name the techniques you use to prioritize a backlog and explain how you agree on priorities with stakeholders?
- Can you explain story points, capacity, and velocity, then describe how you select work for a sprint?
- How would you handle work left over after a sprint?
Can I talk through changes and delivery?
An unplanned requirement during a sprint was among the most asked questions. Check how clearly you can explain your response to a change and what you would tell stakeholders.
- How would you handle an urgent request or growing scope?
- How would you address team disagreements or resistance to a new practice?
- Can you explain how you work with QA, test frequent builds, and use the definition of done?
What should I check about metrics, Jira, and scaled Agile?
These questions go beyond Scrum events and sprint planning. Use them to check whether you can explain tools, results, and work across teams.
- Which delivery and quality metrics would you use to find bottlenecks and assess improvement?
- Can you explain how you set up Jira boards, workflows, and reports?
- Can you describe SAFe implementation, PI Planning, and coordination across teams?
- Can you explain business analyst responsibilities in scaled Agile and describe the Spotify model?
Who gets asked Agile and Scrum
The 20 most asked Agile and Scrum questions
Counted by interview, not by mention: a question asked twice in one conversation counts once.
How do Agile and Waterfall differ in their approach, team roles, and development cadence?
Asked in 9 of 81 interviews · last asked Sep 9 · Concept · Junior
Show answer
Agile develops software in small steps, using frequent feedback to adjust plans. Waterfall follows planned phases, usually with a main release near the end. Agile teams share work across skills; Waterfall more often separates specialist roles with handoffs. Agile uses short cycles or continuous flow, while Waterfall moves through requirements, design, development, and testing.
- Agile suits changing needs and supports early delivery of useful software.
- Waterfall can suit stable requirements and clear phase approvals.
- Agile uses frequent customer feedback; Waterfall usually gathers requirements mainly upfront.
- Scrum defines specific accountabilities, but not all Agile teams use Scrum.
What the interviewer checks: The interviewer checks whether you understand how each approach handles planning, teamwork, delivery, and change.
Other ways it was asked
- “How do you compare waterfall and agile development?”
- “How do waterfall and agile development differ?”
- “What are the fundamental differences between Waterfall and Agile?”
What are the different Scrum ceremonies?
Asked in 6 of 81 interviews · last asked Sep 3 · Concept · Junior
Show answer
Scrum has five formal events: the Sprint, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. The Sprint contains the other four events and lasts one month or less. The Daily Scrum happens every working day; the other three happen once per Sprint.
- Sprint Planning sets the Sprint Goal, selects work, and creates a delivery plan.
- The Daily Scrum is a 15-minute event for Developers to check progress and adapt their plan.
- The Sprint Review gathers stakeholder feedback on results and helps decide what to do next.
- The Sprint Retrospective identifies ways to improve quality and team effectiveness.
What the interviewer checks: The interviewer checks whether you understand each event’s purpose, not just its name.
Other ways it was asked
- “What are the Scrum ceremonies?”
- “What are the main Scrum ceremonies, and which do you use most often?”
- “Which Scrum ceremonies are you familiar with?”
How do Scrum and Kanban differ in team roles, workflow, and delivery cadence?
Asked in 5 of 81 interviews · last asked Sep 10 · Concept · Mid-level
Show answer
Scrum defines three accountabilities: Product Owner, Scrum Master, and Developers. Work happens in fixed-length Sprints around a Sprint Goal. Kanban requires no new roles and manages continuous flow by limiting work in progress. Scrum allows releases during a Sprint, while Kanban has no required delivery schedule.
- Scrum Sprints last one month or less; Kanban does not require Sprints.
- Scrum suits teams that benefit from regular planning, goals, and review.
- Kanban suits work with frequent arrivals and changing priorities, such as support.
- Scrum teams can also use Kanban practices to improve flow.
What the interviewer checks: The interviewer checks whether you understand roles, workflow, delivery timing, and when each approach fits.
Other ways it was asked
- “What are the fundamental differences between Kanban and Scrum?”
- “What is the difference between Kanban and Scrum, and which kind of projects use which?”
- “What other differences are there between Scrum and Kanban?”
What is Agile, and how does it structure software development?
Asked in 5 of 81 interviews · last asked Oct 22 · Concept · Junior
Show answer
Agile is an approach to software development based on frequent feedback, teamwork, and adapting to change. Teams build and deliver software in small parts, then use feedback to guide what they do next. Agile provides values and principles, while frameworks such as Scrum provide specific roles, events, and rules.
- Deliver working software often instead of waiting for one large release.
- Work closely with customers and adjust plans as needs change.
- Review both the software and how the team works.
- Scrum uses fixed-length sprints; Agile itself does not require sprints.
What the interviewer checks: The interviewer is checking whether you understand incremental delivery, feedback, adaptation, and the difference between Agile and Scrum.
Other ways it was asked
- “What is Agile?”
- “What is Agile, and how is it used in software development?”
- “What is Agile methodology, and how does it guide software development?”
What do you know about Scrum?
Asked in 4 of 81 interviews · last asked Oct 2 · Concept · Junior
Show answer
Scrum is a lightweight framework for solving complex problems, often used in Agile software development. A Scrum Team works in Sprints of one month or less to create usable value. The team checks results and improves its plans and ways of working through regular feedback.
- The Scrum Team has a Product Owner, a Scrum Master, and Developers.
- The Product Owner orders the Product Backlog; Developers decide how to do the work.
- Events include Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective.
- Work must meet the Definition of Done to be part of an Increment.
What the interviewer checks: The interviewer is checking whether you understand Scrum’s purpose, team responsibilities, and feedback cycle.
Other ways it was asked
- “What is Scrum?”
How do you prioritize backlog items, and which prioritization techniques do you use?
Asked in 4 of 81 interviews · last asked Sep 11 · Scenario · Mid-level
Show answer
I order backlog items by customer value, business goals, urgency, risk, dependencies, and effort. I use MoSCoW to group needs or a value-versus-effort comparison to rank items. When requests compete, I compare the impact of delaying each one and explain the trade-offs. The Product Owner remains accountable for the final order, which we review as priorities change.
- Agree on clear criteria with stakeholders instead of prioritizing whoever pushes hardest.
- MoSCoW groups items as Must, Should, Could, or Won’t have this time; it does not fully order them.
- Use team estimates to weigh value against effort, and check dependencies before choosing delivery order.
- Review priorities when feedback, risks, or business goals change.
What the interviewer checks: The interviewer checks whether you make clear, value-based choices and handle competing requests without treating everything as urgent.
Other ways it was asked
- “As a proxy product owner, how did you prioritize backlog items?”
- “How would you prioritize a backlog when multiple stakeholders say their work is urgent?”
- “How would you prioritize 10 user stories? Do you know any prioritization techniques?”
How would you handle an unplanned requirement or change request during a sprint?
Asked in 4 of 81 interviews · last asked Oct 22 · Scenario · Senior
Show answer
I would review the request with the Product Owner and Developers to understand its value, urgency, and impact on the Sprint Goal. If it fits without putting that goal at risk, we can agree to change the sprint scope. Otherwise, the Product Owner orders it in the Product Backlog. I would explain the decision and trade-offs to the client.
- Developers and the Product Owner agree on scope changes; do not add work without discussion.
- Protect the Sprint Goal and do not lower quality to fit more work.
- Discuss what planned work may need to move out before accepting new work.
- Only the Product Owner can cancel the sprint if its goal becomes obsolete.
What the interviewer checks: The interviewer checks whether you can respond to change while protecting the Sprint Goal and setting clear expectations.
Other ways it was asked
- “How would you handle a client's change request during a sprint?”
- “How should you agree on a change request with a client during a sprint?”
- “Suppose you're working in a two-week sprint and a new high-priority requirement comes up that you want to include in the sprint. How would you handle that?”
Can you walk me through how you would convert a stakeholder request into a development-ready user story?
Asked in 3 of 81 interviews · last asked Aug 5 · Scenario · Mid-level
Show answer
I first clarify who needs the change, what problem it solves, and why it matters. I write the story as: “As a [user], I want [goal], so that [benefit].” I agree on clear, testable acceptance criteria with the stakeholder. Then I refine it with the team, resolve open questions, identify dependencies, and split it if needed.
- Focus on the user’s problem and value, not just the requested solution.
- Acceptance criteria cover expected behavior and important edge cases.
- Keep the story small enough to finish within one Sprint.
- Confirm shared understanding, estimate with developers, and agree on priority with the Product Owner.
What the interviewer checks: The interviewer checks whether you can turn a vague request into clear, testable work the team understands.
Other ways it was asked
- “Walk me through how you would convert a stakeholder request into development-ready user stories.”
- “How would you turn a stakeholder's needs into a user story?”
How do you estimate user stories, and how do story points work?
Asked in 3 of 81 interviews · last asked Sep 30 · Concept · Mid-level
Show answer
I estimate stories with the developers by discussing the work, comparing it with known stories, and using planning poker to agree on a size. Story points show relative size, considering effort, complexity, and uncertainty, not fixed hours. I split large or unclear stories before estimating. Scrum does not require story points; teams can use other methods.
- Clarify the story and its acceptance criteria before estimating.
- Use a shared scale, such as Fibonacci numbers, and discuss differences in estimates.
- Points are team-specific; do not compare them across teams or use them to rate people.
- Past completed points can help forecast future work, but they are not a delivery promise.
What the interviewer checks: The interviewer checks whether you understand relative sizing, team discussion, and the limits of estimates.
Other ways it was asked
- “How do you estimate work in Scrum, using story points or another approach?”
- “How do you estimate work using story points?”
- “Why use story points to estimate work?”
Which Agile methodologies and frameworks do you know, and when would you use them?
Asked in 2 of 81 interviews · last asked Aug 4 · Concept · Junior
Show answer
I know Scrum, Kanban, Extreme Programming (XP), Lean, and SAFe. I use Scrum for work in short sprints and Kanban for a steady flow of changing requests. XP supports strong coding practices, while Lean helps reduce waste. I would consider SAFe when many teams need coordination, but only if its added structure fits the organization.
- Scrum uses Sprint Goals, clear responsibilities, and regular feedback.
- Kanban limits work in progress and improves flow without requiring sprints.
- XP emphasizes practices such as automated testing, pair programming, and continuous integration.
- Choose based on team needs; scaling frameworks add coordination but also overhead.
What the interviewer checks: The interviewer is checking whether you can choose a suitable approach, not just name frameworks.
Other ways it was asked
- “What are agile methodologies, and when would you use them?”
- “What methodologies or frameworks are used in Agile project management, including Scrum?”
- “What Agile methodologies or frameworks are commonly used?”
How should a daily Scrum stand-up be run, and what is its purpose?
Asked in 2 of 81 interviews · last asked Oct 13 · Concept · Junior
Show answer
The Daily Scrum is a 15-minute meeting for Developers to check progress toward the Sprint Goal and adjust their plan. It happens at the same time and place each working day. Developers choose the format, discuss blockers, and agree on next steps. It is not a status report to a manager; detailed discussions happen afterward.
- Focus on progress toward the Sprint Goal, not just listing completed tasks.
- Developers run the meeting; the Scrum Master does not need to lead it.
- The three-question format and standing up are optional.
- Identify blockers during the meeting; follow up on detailed problem-solving afterward.
What the interviewer checks: The interviewer checks whether you understand daily planning, team ownership, and the difference between coordination and status reporting.
Other ways it was asked
- “What is the purpose of daily stand-ups, and how should they be run?”
What is the Scrum Master’s role in facilitating Scrum events and processes?
Asked in 2 of 81 interviews · last asked Aug 4 · Concept · Junior
Show answer
The Scrum Master helps the team understand and use Scrum effectively. They ensure Scrum events happen, stay within their time limits, and are useful. They coach the team, help remove blockers, and support improvement. They do not assign tasks or need to lead every event.
- Help everyone understand Scrum and support the Scrum Team’s effectiveness.
- Ensure events are useful and stay within their time limits.
- Support self-management rather than direct the team’s work.
- Help remove blockers; Developers run their own Daily Scrum.
What the interviewer checks: The interviewer checks whether you understand that a Scrum Master coaches and supports the team rather than manages it.
Other ways it was asked
- “What is the role of a Scrum Master?”
- “Which role is responsible for facilitating Scrum events and processes?”
What is a user story?
Asked in 2 of 81 interviews · last asked Jun 8 · Concept · Junior
Show answer
A user story is a short description of a user’s need and why it matters, written from their point of view. It helps the team discuss what to build, rather than giving a full specification. Acceptance criteria describe what must be true for the story to be accepted.
- A common format is: As a [user], I want [goal], so that [benefit].
- The story starts a conversation; the team adds details together.
- Acceptance criteria make the expected result clear and testable.
- User stories are common in Agile, but Scrum does not require them.
CodeAs a customer, I want to reset my password so that I can regain access to my account. Acceptance criterion: A valid reset link lets me set a new password.What the interviewer checks: The interviewer is checking whether you understand user needs, value, and how stories guide team discussion.
How do you create, define, and prioritize backlog items from requirements?
Asked in 2 of 81 interviews · last asked Sep 30 · Scenario · Senior
Show answer
I clarify requirements with stakeholders, then turn them into backlog items with clear acceptance criteria. I split large items, such as epics, into smaller pieces that deliver value and work with developers to estimate effort. The Product Owner orders the backlog using value, risk, dependencies, and effort, then updates it as feedback arrives.
- Clarify the user need and expected outcome before defining a solution.
- Define acceptance criteria so the team knows what each item must achieve.
- Split large items into pieces small enough to complete within a Sprint.
- The Product Owner is accountable for backlog ordering, with input from stakeholders and developers.
What the interviewer checks: The interviewer checks whether you can turn requirements into clear, manageable work and explain how priorities are decided.
Other ways it was asked
- “How are backlog tasks and epics typically created, prioritized, and defined on a software team?”
- “How do you create and prioritize a backlog based on requirements?”
How do you organize backlog refinement in an Agile team?
Asked in 2 of 81 interviews · last asked Jul 22 · Scenario · Senior
Show answer
I organize backlog refinement as regular, short discussions between the Product Owner and Developers. We clarify upcoming items, split large ones, discuss value and dependencies, and size the work. The Product Owner orders the backlog, while Developers own sizing. Refinement is ongoing work, not a required Scrum event, and helps us prepare for Sprint Planning.
- Focus on items likely to be selected soon, rather than detailing the whole backlog.
- The Product Owner owns backlog ordering; Developers own sizing.
- Agree on clear expectations and split items small enough to finish within a Sprint.
- Invite stakeholders or specialists when their input helps clarify the work.
What the interviewer checks: The interviewer is checking whether you make upcoming work clear through collaboration without treating refinement as a fixed Scrum ceremony.
Other ways it was asked
- “What is backlog refinement in Scrum, and how does it fit into the process?”
How do you decide which backlog items to include in a sprint?
Asked in 2 of 81 interviews · last asked Sep 10 · Scenario · Mid-level
Show answer
I select backlog items with the team based on the Sprint Goal, business value, and available capacity. During Sprint Planning, the Product Owner explains priorities, and the Developers select the work after discussing scope. We consider estimates, dependencies, and what we can realistically finish to the Definition of Done.
- Select items that support the Sprint Goal, not just the highest-ranked items.
- The Product Owner orders the backlog; Developers select the items for the sprint.
- Use available capacity, past performance, and estimates to guide the forecast.
- Check dependencies and clarity, and include time for testing and other work needed to finish.
What the interviewer checks: The interviewer checks whether you balance value and realistic delivery while respecting Scrum roles.
Other ways it was asked
- “How would you decide which tasks to select from the backlog for a sprint?”
- “How did you decide which work to include in a sprint?”
How would you resolve a disagreement between team members during a sprint?
Asked in 2 of 81 interviews · last asked Oct 22 · Scenario · Mid-level
Show answer
I would address the disagreement early, not wait for the retrospective. I would hear both sides, keep the discussion respectful, and help them compare options against the facts and the Sprint Goal. If they remain stuck, I would involve the right person to help, such as the Scrum Master. We could use the retrospective to discuss preventing similar issues.
- Focus on the issue, not the people.
- Use shared criteria, evidence, or a short test to compare options.
- Agree on a next step and check whether it resolves the issue.
- The Scrum Master can help the discussion but does not decide technical choices for the team.
What the interviewer checks: The interviewer is checking whether you handle conflict promptly and fairly while helping the team keep moving.
Other ways it was asked
- “How would you handle a situation where, within a sprint, there is a disagreement between two developers or two QA people?”
- “Would you wait until the retro in two weeks to resolve a disagreement at the start of a sprint?”
What is the business analyst’s role within a SAFe Agile team?
Asked in 2 of 81 interviews · last asked Aug 5 · Concept · Mid-level
Show answer
A business analyst helps a SAFe Agile team understand business needs and turn them into clear, testable requirements. They work with the Product Owner, stakeholders, and team to refine stories, define acceptance criteria, and clarify questions. They also help check that the solution meets business needs.
- Support the Product Owner; the Product Owner remains responsible for prioritizing the team backlog.
- Connect stakeholders and the team to build a shared understanding of requirements.
- Help identify business rules, dependencies, and gaps before and during development.
- SAFe does not require a separate business analyst role; teams may share these responsibilities.
What the interviewer checks: The interviewer is checking whether you understand how business analysis supports delivery without replacing the Product Owner.
How do you apply Agile methodology when managing a project?
Asked once · last asked Sep 15 · Scenario · Mid-level
Show answer
I apply Agile by setting a clear goal, ordering work by value, and delivering small, usable pieces often. I work with the team and stakeholders to review results and adjust priorities as we learn. I make progress and blockers visible, and help the team improve how it works.
- Keep a clear project goal and a prioritized backlog.
- Deliver small, usable pieces and get feedback early.
- Let the team plan its work; help remove blockers.
- Review progress and improve the process regularly, not just at the end.
What the interviewer checks: The interviewer is checking whether you can turn Agile principles into daily project decisions, not just name meetings.
On what basis do you decide whether a project should follow Waterfall or Agile?
Asked once · last asked May 3 · Scenario · Mid-level
Show answer
I choose based on how clear the requirements are, how likely they are to change, and how often users can give feedback. Waterfall fits stable requirements with clear stages and approvals. Agile fits changing needs where we can deliver small parts and learn from feedback. I also consider risks, contracts, and compliance needs.
- Stable, well-understood requirements favor Waterfall; uncertainty and frequent change favor Agile.
- Agile needs regular user feedback and work that can be delivered in small parts.
- Consider delivery risks, team readiness, contracts, and approval needs.
- Compliance does not automatically require Waterfall; Agile can include documentation and controls.
What the interviewer checks: The interviewer is checking whether you match the approach to the project rather than always choosing one method.
Agile fundamentals and methodology interview questions
Compare Agile, Scrum, Kanban, and Waterfall, and explain Agile principles, benefits, and its place in software development. 17 questions.
What are the principles of agile development, and how would you apply them in a software project?
Asked once · last asked May 19 · Concept · Mid-level
Other ways it was asked
- “Can you explain the principles of agile development and how you have applied them in your projects?”
How does Kanban represent work compared with Scrum's Product Backlog and Increment?
Asked once · last asked Sep 10 · Concept · Mid-level
Which Agile methodology do you apply to define and develop requirements, and how do you use it in practice?
Asked once · last asked Oct 2 · Concept · Mid-level
Why would you choose Kanban for managing a project?
Asked once · last asked Jan 6 · Behavioral · Mid-level
Other ways it was asked
- “Why did you choose the Kanban method for managing a project?”
What differences do you see when moving from a hybrid Waterfall-Agile model to an Agile delivery model?
Asked once · last asked Oct 23 · Concept · Mid-level
What do you think the benefits of Agile are?
Asked once · last asked Jul 16 · Concept
What software development methodologies are used besides Agile?
Asked once · last asked Aug 4 · Concept · Junior
Why do we use a Kanban board or Scrum?
Asked once · last asked Aug 17 · Concept · Junior
Can you explain the software development life cycle (SDLC) and how Agile fits into it?
Asked once · last asked Aug 26 · Concept · Junior
What are the pros and cons of different software development methodologies?
Asked once · last asked Sep 2 · Concept
Other ways it was asked
- “What software development methodologies have you worked with, and what are their pros and cons?”
How does Kanban work?
Asked once · last asked Sep 10 · Concept · Junior
Scrum roles and ceremonies interview questions
Questions cover Scrum principles, team responsibilities, sprints, stand-ups, reviews, retrospectives, and how teams organize their work. 19 questions.
What are the key Scrum ceremonies, and what is a business analyst's role in each?
Asked once · last asked Mar 16 · Concept · Mid-level
How does a user story typically move through a Scrum team, from product ownership and development through sprint review and retrospective?
Asked once · last asked May 13 · Concept · Mid-level
How do you structure a typical project-management week, including Scrum activities?
Asked once · last asked Jul 16 · Scenario · Mid-level
How are the Scrum Master and Product Manager roles different?
Asked once · last asked Sep 30 · Concept · Mid-level
How should a project coordinator work with the Scrum master, Agile teams, project manager, and stakeholders?
Asked once · last asked Oct 9 · Concept · Mid-level
How do you distinguish Scrum Master responsibilities from Project Manager responsibilities on a project?
Asked once · last asked Oct 23 · Concept · Mid-level
Tell me about an improvement you implemented based on team feedback during a retrospective.
Asked once · last asked Oct 23 · Behavioral
What are the different principles of Scrum?
Asked once · last asked Jun 17 · Concept · Junior
Other ways it was asked
- “How many principles of Scrum are there?”
Can you describe an agile team?
Asked once · last asked Feb 11 · Concept · Junior
What is a sprint?
Asked once · last asked May 9 · Concept · Junior
What do you think is most important when working on a Scrum team?
Asked once · last asked May 13 · Concept
What are backlog grooming, sprint reviews, and retrospectives?
Asked once · last asked Aug 4 · Concept · Junior
Show 3 more
What is your understanding of the technical product owner role and what are they responsible for in the life cycle of a sprint?
Asked once · last asked Sep 14 · Concept · Mid-level
What ceremonies should a technical product owner be responsible for?
Asked once · last asked Sep 14 · Concept · Junior
What does a good sprint review look like to you?
Asked once · last asked Sep 14 · Concept · Mid-level
User stories and acceptance criteria interview questions
Turn business needs into user stories, split epics, write acceptance criteria, and explain how stories differ from tasks and use cases. 8 questions.
How do you work with user stories, understand business needs, and prioritize the work?
Asked once · last asked Feb 19 · Behavioral · Mid-level
What is the difference between an epic and a task?
Asked once · last asked Jun 17 · Concept · Junior
Can you create a sample user story and acceptance criteria for checking a patient’s insurance eligibility?
Asked once · last asked Aug 5 · Case · Mid-level
What’s your process for making sure the acceptance criteria are correct and tight enough for developers and testers?
Asked once · last asked Sep 1 · Scenario · Mid-level
What is the difference between a user story and a use case?
Asked once · last asked Sep 9 · Concept · Junior
How would you break down the epic “A user can place an order on a website” into individual user stories?
Asked once · last asked Sep 28 · Scenario · Mid-level
Product backlog and prioritization interview questions
Explain how you build, refine, and prioritize a backlog, agree on priorities with stakeholders, and make room for improvement work. 10 questions.
How do you refine and prioritize backlog items with a product owner in an agile team, and coordinate backend work with frontend requirements?
Asked once · last asked May 21 · Scenario · Mid-level
Tell me about a time you had to reprioritize a backlog quickly. What triggered the change, how did you get alignment, and what was the outcome?
Asked once · last asked Mar 29 · Behavioral · Senior
How would you respond if the backlog had few tasks at first, then became overloaded after about two weeks? How would you prioritize the work?
Asked once · last asked Apr 20 · Scenario · Mid-level
How do you work in an Agile process, and how do you collaborate with the product owner (PO) on product backlog items (PBIs)?
Asked once · last asked May 21 · Scenario · Mid-level
What would you do if improvement ideas kept getting added to the backlog but never made it into a sprint because the team was always focused on deliverables?
Asked once · last asked May 22 · Scenario · Senior
How do you manage a project backlog?
Asked once · last asked Jul 29 · Behavioral · Mid-level
Who is responsible for prioritizing user stories in Scrum: the development team or the Product Owner?
Asked once · last asked Feb 19 · Concept · Junior
Other ways it was asked
- “Who is responsible for prioritizing user stories: you or the Product Owner?”
Agile estimation and sprint planning interview questions
Planning questions cover story points, estimation, spikes, capacity, velocity, sprint length, work selection, task assignment, and unfinished work. 21 questions.
How do you work with an engineering team to plan, estimate, and execute work, and what tools or artifacts do you use?
Asked once · last asked Jul 24 · Behavioral · Mid-level
Why use story points instead of hours or days, and should you convert between them?
Asked once · last asked Sep 30 · Concept · Mid-level
Other ways it was asked
- “Why do Agile teams use story points instead of estimating work directly in hours?”
- “Why might a team equate one story point with one day, and why might story points instead remain independent of hours?”
What is a spike in Agile, and when would you use one?
Asked once · last asked Jun 9 · Concept · Mid-level
How do you determine the appropriate duration for a sprint?
Asked once · last asked Jul 16 · Concept · Mid-level
How do you manage work that spills over from one sprint to the next?
Asked once · last asked Jul 16 · Scenario · Mid-level
Why use a 1, 3, 5, 7, 9 scale for story points, and why might 9 be omitted?
Asked once · last asked Aug 4 · Concept · Mid-level
What is the Fibonacci sequence, and why is it used for story-point estimation?
Asked once · last asked Aug 4 · Concept · Mid-level
What are the project manager’s and tech lead’s responsibilities during sprint planning?
Asked once · last asked Sep 3 · Scenario · Mid-level
Other ways it was asked
- “When planning a sprint for a team of five developers and one tech lead, what would your responsibilities as the project manager be, and what would the tech lead be responsible for?”
- “During sprint planning, what responsibilities would you take on as the project manager?”
How do you estimate a team's capacity and velocity?
Asked once · last asked Sep 3 · Scenario · Mid-level
How does Scrum estimation using a weighted average of estimates work?
Asked once · last asked Dec 11 · Concept · Mid-level
During sprint planning, who decides which tasks to include in the sprint and who takes each task?
Asked once · last asked Sep 10 · Concept · Mid-level
How would you assign and estimate tickets in an Agile project, and how does that process differ from Waterfall?
Asked once · last asked Sep 30 · Scenario · Mid-level
Show 7 more
How should a project manager determine a team's relationship between story points and elapsed time?
Asked once · last asked Sep 30 · Concept · Mid-level
How would you contribute to estimating the complexity and delivery time of a project or feature with your team?
Asked once · last asked Mar 19 · Scenario · Mid-level
How should a team estimate admin-panel tasks: should the relevant front-end developer estimate them, or should the whole team contribute?
Asked once · last asked Mar 19 · Scenario · Mid-level
How should a team decide whether to assign tasks directly or leave them in the backlog for developers to pick up?
Asked once · last asked Mar 19 · Scenario · Mid-level
How would you classify tasks by complexity, for example as simple or difficult?
Asked once · last asked May 7 · Scenario · Mid-level
How do you organize project work in sprints?
Asked once · last asked Aug 12 · Concept · Mid-level
How do you handle sprint planning for assets?
Asked once · last asked Aug 14 · Scenario · Mid-level
Agile change management and teamwork interview questions
Work through questions about changing requirements, urgent requests, growing scope, team disagreements, resistance to new practices, and stakeholder communication. 11 questions.
How would you handle a critical regulatory requirement mid-sprint, including any scope trade-offs?
Asked once · last asked May 3 · Scenario · Mid-level
Other ways it was asked
- “What would you do if a critical regulatory requirement emerged in the middle of a sprint?”
- “When a critical regulatory requirement arises mid-sprint, would you swap user stories or make another trade-off?”
When a critical regulatory requirement arises mid-sprint, what role should the Scrum Master play, and why?
Asked once · last asked May 3 · Scenario · Mid-level
How do you handle scope creep when stakeholders keep changing requirements in the middle of a sprint?
Asked once · last asked May 3 · Scenario · Mid-level
When priorities change mid-sprint in a remote setting, what criteria do you use to rescope, renegotiate deadlines, and communicate tradeoffs so everyone stays aligned?
Asked once · last asked Sep 10 · Scenario · Mid-level
How would you handle team members' resistance when introducing Agile practices or Jira updates?
Asked once · last asked Sep 14 · Scenario · Senior
How would you handle a late-sprint stakeholder change affecting both backend workflows and the React UI, including what questions you would ask and how you would drive a decision?
Asked once · last asked Sep 23 · Scenario · Senior
Other ways it was asked
- “How do you handle a late-sprint stakeholder change affecting both back end workflows and the React UI? What questions do you ask, and how do you drive a decision?”
If a high-priority production issue affects the scope of a sprint during a typical two-week Agile cycle, how would you handle it and communicate about it to business stakeholders and the wider audience?
Asked once · last asked Oct 9 · Scenario · Mid-level
How do you deal with short deadlines and a lack of strict processes in a very agile environment?
Asked once · last asked Sep 24 · Scenario · Mid-level
How do you handle rapidly changing functional and technical requirements in a fast-paced enterprise environment?
Asked once · last asked Sep 29 · Scenario
Agile testing and release management interview questions
Discuss QA collaboration, testing frequent builds, the definition of done, feature demos, branching strategies, and releases in small steps. 8 questions.
What is your go-to approach for setting up a branching strategy for a project, particularly when developing in Agile sprints?
Asked once · last asked Feb 17 · Scenario · Mid-level
How would you analyze and test a new build delivered every two or three weeks during a sprint?
Asked once · last asked Mar 17 · Scenario · Mid-level
How do you typically approach building and quickly demoing a feature to get stakeholder feedback?
Asked once · last asked Mar 24 · Scenario · Mid-level
How would you use Scrum to deliver changes to production iteratively, determine release frequency, and organize the release process?
Asked once · last asked May 28 · Behavioral · Mid-level
Other ways it was asked
- “How did your team use Scrum to deliver changes to production iteratively, how often were releases made, and what did the release process involve?”
When requirements are still changing, when should development be considered complete and tickets handed over to QA?
Asked once · last asked Jul 16 · Scenario · Mid-level
How would you contribute to Agile ceremonies as a QA engineer so that the whole team embraces quality?
Asked once · last asked Jul 16 · Scenario · Mid-level
What is your definition of done for a story to be considered complete and pushed into production?
Asked once · last asked Oct 9 · Concept · Mid-level
How would you organize testing activities during a sprint?
Asked once · last asked Oct 24 · Behavioral · Mid-level
Other ways it was asked
- “How does your general sprint testing process work? What kind of work do you do during a sprint?”
Agile metrics and Jira interview questions
These questions ask about delivery and quality metrics, bottlenecks, improvement, and setting up Jira boards, workflows, and reports. 7 questions.
How would you configure Jira for a team or portfolio, including boards, issue types, workflows, and prioritization rules?
Asked once · last asked Mar 29 · Tooling · Mid-level
Other ways it was asked
- “How have you configured Jira for a team or portfolio, including boards, issue types, workflows, and prioritization rules?”
After five sprints, your manager asks for an objective metric showing that the team's performance is improving. What metric would you propose?
Asked once · last asked May 7 · Scenario · Mid-level
Why might story points indicate team performance trends better than other metrics?
Asked once · last asked May 7 · Concept · Mid-level
Which agile flow and code-quality metrics would you track, who should monitor cumulative flow diagrams and bottlenecks, and how would you assess code quality's impact?
Asked once · last asked Jul 16 · Scenario · Senior
How would you use Jira data to estimate team capacity and select tasks for sprint planning?
Asked once · last asked Sep 3 · Tooling · Mid-level
Which Agile delivery metrics do you track on a project, and how do you use them?
Asked once · last asked Oct 5 · Concept · Mid-level
What do you know about Jira?
Asked once · last asked Jun 17 · Tooling · Junior
SAFe and scaled Agile interview questions
Explore SAFe, PI Planning, business analyst responsibilities, coordination across teams and portfolios, and the Spotify model. 5 questions.
Which governance structures, such as Scrum of Scrums, functional-owner meetings, or steering committees, would you use to coordinate a project?
Asked once · last asked Jul 16 · Scenario · Senior
What preparation would you do for PI Planning, and what responsibilities would you have during the event?
Asked once · last asked Aug 5 · Scenario · Senior
How would you implement SAFe at scale?
Asked once · last asked Oct 22 · Behavioral · Senior
Other ways it was asked
- “How have you implemented SAFe at scale?”
- “When implementing SAFe at scale, what did not work as expected, and what surprised you by working well?”
What is the Spotify model, and how does its tribe-and-squad structure work?
Asked once · last asked Sep 28 · Concept · Mid-level
Related interview questions
- Project Manager interview questions
- Software Engineer interview questions
- QA Engineer interview questions
- Business Analyst interview questions
- Data Engineer interview questions
- Product Manager interview questions
- Manual Testing interview questions
- Automation Testing interview questions
- API Testing interview questions
- Salesforce interview questions
How this list is made
Every question here was asked by a real interviewer in a real job interview that a candidate ran MeetAssist in. After the call, the interviewer's questions are pulled from the transcript. Practice sessions, tests, exams and anything that was not a job interview are dropped.
Questions are rewritten so they make sense on their own: names of people, employers and clients are removed, and speech-to-text mistakes are fixed. Small talk, logistics and questions about one candidate's own résumé are left out. Rephrasings of the same question are merged, and the count is the number of different interviews it came up in.
The interviews come from candidates who use MeetAssist, so they lean towards software, data and AI roles: the shares describe these interviews, not every Agile and Scrum interview. Answers to the most asked questions are written and checked by an editor; a "common mistake" is shown only when reviews of real answers in these interviews show it, with the count.
81 interviews, 61 candidates, Dec 2025 to Oct 2026. Updated every month with new interviews.
Or add the Chrome extension