50 Agile & Scrum Interview Questions (With Answers)

Agile and Scrum are the dominant software delivery frameworks. Interviews test your understanding of Agile values, Scrum ceremonies, roles, estimation, metrics, and scaling frameworks. This guide covers the 50 most common questions — with concise, practical answers.

Quick reference

Agile Fundamentals

1. What is Agile and what are the four values of the Agile Manifesto?

Agile is an iterative approach to software development that delivers value incrementally through collaboration, feedback, and adaptability.

The Agile Manifesto (2001) defines four core values:

Both sides have value — the right side is not worthless. Agile simply prioritises the left side.

2. What are the 12 Agile Principles?

The 12 principles behind the Agile Manifesto:

1. Highest priority is customer satisfaction through early, continuous delivery of valuable software
2. Welcome changing requirements, even late in development
3. Deliver working software frequently (weeks rather than months)
4. Business people and developers must work together daily
5. Build projects around motivated individuals; give them the environment and trust they need
6. Face-to-face conversation is the most efficient way to convey information
7. Working software is the primary measure of progress
8. Agile promotes sustainable development at a constant pace
9. Continuous attention to technical excellence and good design enhances agility
10. Simplicity — the art of maximising the work not done — is essential
11. Self-organising teams produce the best architectures, requirements, and designs
12. Regularly reflect on how to become more effective and adjust accordingly

3. Agile vs Waterfall — what are the key differences?

4. What are the main Agile frameworks?

5. What is the difference between Agile and Scrum?

Agile is a philosophy/mindset — a set of values and principles for iterative software delivery.

Scrum is a specific framework that implements Agile. It defines:

• 3 roles (Product Owner, Scrum Master, Developers)
• 5 events (Sprint, Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective)
• 3 artifacts (Product Backlog, Sprint Backlog, Increment)

All Scrum teams are Agile, but not all Agile teams use Scrum.

Scrum Framework

6. What are the three roles in Scrum?

The Scrum Guide (2020) replaced "Development Team" with "Developers" and removed sub-roles to emphasise whole-team accountability.

7. What are the five Scrum events?

8. What are the three Scrum artifacts?

9. What is a Sprint and how long should it be?

A Sprint is a fixed-length event (≤4 weeks) in which the Scrum team creates a usable, potentially releasable Increment.

Sprint length considerations:

A Sprint should never be changed or cancelled mid-sprint except by the Product Owner when the Sprint Goal becomes obsolete.

10. What is the Sprint Goal?

The Sprint Goal is a single, concise objective that the Scrum Team commits to achieve during the Sprint. It:

• Provides focus and flexibility for the team
• Is created during Sprint Planning
• Guides the team in selecting which backlog items to work on
• Allows adaptation of the Sprint Backlog without changing the Sprint Goal

Example Sprint Goal:
"Enable customers to track their order status in real time."

11. What happens in Sprint Planning?

Sprint Planning produces two things:

1. A Sprint Goal — Why is this Sprint valuable?
2. A Sprint Backlog — What can be Done and How will it be done?

The meeting has three questions:

• Why is this Sprint valuable? (PO explains value; team crafts Sprint Goal)
• What can be Done? (Developers forecast which PBIs are achievable)
• How will the chosen work be done? (Developers decompose PBIs into tasks)

12. What is the Daily Scrum and what are its goals?

The Daily Scrum is a 15-minute event for Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog.

The classic format (not mandated by 2020 Scrum Guide):

• What did I do yesterday that helped the team meet the Sprint Goal?
• What will I do today to help the team meet the Sprint Goal?
• Do I see any impediments that prevent me or the team from meeting the Sprint Goal?

The Scrum Master ensures it happens, but Developers run it. It's not a status meeting for management.

13. What is a Sprint Review vs a Sprint Retrospective?

Product Backlog & User Stories

14. What is a Product Backlog Item (PBI)?

A Product Backlog Item is a unit of work in the Product Backlog. PBIs can be:

• User Stories — feature-focused, customer perspective
• Bugs — defects to fix
• Technical debt — refactoring, infrastructure improvements
• Spikes — research tasks to reduce uncertainty
• Epics — large stories that need decomposition

15. What is a User Story and what is the INVEST criteria?

A User Story is a short description of a feature from the perspective of the user:

As a [type of user],
I want [some goal]
so that [some reason/benefit].

Example:

As a registered customer,
I want to reset my password via email
so that I can regain access to my account if I forget it.

INVEST criteria for a good user story:

16. What are Acceptance Criteria?

Acceptance Criteria define the conditions that must be met for a User Story to be accepted. They:

• Are written in collaboration between PO and developers
• Are testable and measurable
• Define the "what" not the "how"

Common format — Given/When/Then (Gherkin):

Given I am on the login page
When I enter a valid email and click "Reset Password"
Then I receive an email with a reset link within 2 minutes

17. What is the Definition of Done (DoD)?

The Definition of Done is a shared understanding of what "Done" means — the criteria that every Increment must meet before it can be released.

Example DoD:

• Code reviewed and approved by ≥1 peer
• Unit tests written and passing (≥80% coverage)
• Integration tests passing
• No known critical or high bugs
• Documentation updated
• Deployed to staging environment
• Product Owner accepted

The DoD ensures transparency and prevents undone work from accumulating.

18. What is the difference between Definition of Done and Acceptance Criteria?

19. What is Backlog Refinement (Grooming)?

Backlog Refinement is an ongoing activity where the Product Owner and Developers review and prepare upcoming backlog items. Activities include:

• Adding detail, estimates, and order to PBIs
• Breaking down large stories (Epics) into smaller stories
• Removing outdated or irrelevant items
• Confirming acceptance criteria

Not a formal Scrum event, but recommended. Teams spend ≤10% of Sprint capacity on refinement.

20. How should the Product Backlog be prioritised?

The PO orders the backlog based on multiple factors:

Common techniques: MoSCoW (Must/Should/Could/Won't), WSJF (Weighted Shortest Job First in SAFe), Kano Model.

Estimation

21. What are Story Points and why use them?

Story Points are a relative unit for estimating the effort, complexity, and uncertainty of a User Story. They are not time (hours/days).

Why relative estimation?

• Teams estimate consistently against each other (not against absolute time)
• Accounts for uncertainty and risk
• Improves over time as the team calibrates

Fibonacci sequence is commonly used: 1, 2, 3, 5, 8, 13, 21, 40, 100

22. What is Planning Poker?

Planning Poker is a consensus-based estimation technique:

1. PO presents a User Story
2. Each team member privately selects a card with their estimate
3. All cards are revealed simultaneously
4. Outliers explain their reasoning
5. Discussion and re-estimation until consensus

The simultaneous reveal prevents anchoring bias (one person influencing others).

23. What is Velocity and how is it used?

Velocity is the average number of story points a team completes per Sprint. It is used for:

• Release planning — "We have 200 points of work; at 40 pts/sprint we need 5 sprints"
• Sprint planning — team selects work up to their historical velocity
• Trend monitoring — declining velocity may signal process issues

Velocity is a planning tool, not a performance measure. Never compare velocities between teams.

24. What is a Burndown Chart?

A Sprint Burndown Chart shows work remaining (story points or tasks) over time within a Sprint.

Points
remaining
  40 |*
  30 |  *
  20 |    *  *
  10 |        *  *
   0 |              *
     Day: 1  3  5  7  9  10
          ─────────────────
          Ideal  ........

• Ideal line — linear reduction to zero
• Actual line — real remaining work
• Rising actual line = work being added or discovered
• Flat actual line = work not progressing

A Release Burndown tracks remaining work across multiple Sprints.

25. What is the difference between Velocity and Throughput?

Kanban

26. What is Kanban and how does it differ from Scrum?

Kanban is a pull-based workflow management method that visualises work and limits work in progress to improve flow.

27. What is a WIP Limit and why is it important?

A Work-In-Progress (WIP) limit caps the number of items allowed in a workflow column simultaneously.

Why WIP limits matter:

• Expose bottlenecks — if a column is always at its limit, it's a constraint
• Reduce context switching — focus on finishing over starting
• Improve flow — less multitasking means faster throughput
• Make problems visible — queues become obvious

Example Kanban board with WIP limits:

28. What is Cumulative Flow Diagram (CFD)?

A Cumulative Flow Diagram shows the number of items in each workflow stage over time. It helps identify:

• Bottlenecks — bands widen in the stuck stage
• Cycle time — horizontal distance between "started" and "done" bands
• Work in progress — vertical distance between bands
• Throughput — slope of the "Done" line

Scrum Roles Deep Dive

29. What does a Scrum Master do?

The Scrum Master serves the Team, the Product Owner, and the Organisation:

Serves the Developers:

• Coaches self-management and cross-functionality
• Helps focus on high-value Increments
• Removes impediments to progress
• Facilitates Scrum events when requested

Serves the Product Owner:

• Helps with Product Goal and backlog techniques
• Facilitates stakeholder collaboration
• Helps the team understand the need for clear PBIs

Serves the Organisation:

• Leads, trains, and coaches Agile adoption
• Plans and advises Scrum implementations
• Removes barriers between stakeholders and teams

30. What are the responsibilities of a Product Owner?

The PO is one person, not a committee. They may represent stakeholder needs but are solely accountable for Product Backlog ordering.

31. Can the Scrum Master and Product Owner be the same person?

No. This creates a conflict of interest:

• The PO pushes for maximum scope
• The Scrum Master protects the team from overcommitment and scope creep

Similarly, Scrum Master and Developer should not be the same person — the SM cannot objectively facilitate a team they are also a member of.

Common Scenario Questions

32. How do you handle a stakeholder who keeps changing requirements mid-Sprint?

1. Educate the stakeholder on Sprint integrity — the Sprint Goal is a commitment
2. Add to the Product Backlog — new items should go through the PO and be prioritised for a future Sprint
3. Escalate to the PO if stakeholders bypass the process
4. If the requirement change is critical enough to invalidate the Sprint Goal, the PO can cancel the Sprint — a rare but valid option
5. Retrospective — identify systemic causes and propose process improvements

33. What do you do when the team misses the Sprint Goal?

1. Don't panic — incomplete items return to the Product Backlog
2. Sprint Review — be transparent with stakeholders about what was completed
3. Retrospective — analyse root causes:
   • Were stories too large?
   • Were there unexpected dependencies?
   • Were external blockers unresolved?
   • Was the Sprint Goal realistic?
4. Adjust — improve estimation, break down stories further, or address systemic issues

Never force incomplete work into "Done" by relaxing the Definition of Done.

34. What is a Technical Spike and when do you use one?

A Spike is a time-boxed investigation to reduce uncertainty or risk:

Spikes are:

• Estimated in story points or hours (not deliverable features)
• Placed in the Sprint Backlog like other work
• Outputs: decision, proof of concept, or documented findings

35. What is an Epic and how does it relate to User Stories?

Hierarchy:

Product Goal
  └── Epic (large body of work)
        └── Feature / Capability
              └── User Story (fits in one Sprint)
                    └── Task (hours)

An Epic is a large User Story that cannot fit in a single Sprint. It is broken down into smaller stories during backlog refinement. Epics may span multiple Sprints or even months.

36. What is the difference between a Bug and Technical Debt?

Agile Metrics

37. What Agile metrics matter most?

Avoid gaming metrics. Velocity should reflect real team capacity, not heroics.

38. What is a Cumulative Velocity and how do you use it for release planning?

Release planning formula:

Remaining work (story points) ÷ Average velocity (points/sprint) = Sprints needed

Example:

• Product Backlog: 320 story points
• Team velocity: 40 points/Sprint
• 320 ÷ 40 = 8 Sprints (approximately 4 months at 2-week sprints)

Add a buffer for:

• Uncertainty: ±20%
• Holidays, absences
• Newly discovered work

Scaling Agile

39. What is SAFe (Scaled Agile Framework)?

SAFe is a framework for applying Agile and Lean at enterprise scale. Key elements:

PI Planning (Program Increment Planning):

• 2-day event every 8–12 weeks
• All ART teams plan together in person or virtually
• Teams identify dependencies, risks, and objectives

40. What is LeSS (Large-Scale Scrum)?

LeSS scales Scrum with minimal additional process:

• 2–8 teams working on a single product
• One Product Owner, one Product Backlog
• One Sprint for all teams simultaneously
• Multi-team Sprint Planning (Part 1: joint, Part 2: per-team)
• Combined Sprint Review
• Separate and Overall Retrospectives

LeSS Huge (8+ teams) adds Area Product Owners for backlog areas.

41. What is Nexus?

Nexus is Scrum.org's scaling framework for 3–9 Scrum teams working on a single product:

• Adds a Nexus Integration Team (Scrum Master + Product Owner + Integration specialists)
• Nexus Sprint Planning, Nexus Daily Scrum, Nexus Sprint Review, Nexus Sprint Retrospective
• Focuses on identifying and resolving integration issues across teams

Continuous Improvement

42. How do you run an effective Retrospective?

A common retrospective format: Start / Stop / Continue

Other formats:

• 4Ls: Liked, Learned, Lacked, Longed For
• Mad / Sad / Glad: Emotional temperature check
• Sailboat: Wind (positives) vs Anchor (negatives) vs Rocks (risks) vs Sun (goals)

Good retrospectives produce 1–3 concrete action items with owners and deadlines.

43. What is the Agile concept of "sustainable pace"?

Sustainable pace (Agile Principle #8): teams should be able to maintain a constant development pace indefinitely.

Signs of unsustainable pace:

• Consistent overtime
• Rising defect rates
• Team burnout and attrition
• Declining velocity over time

Sustainable pace leads to:

• Better quality (no cutting corners)
• Lower defect rates
• Team retention
• Consistent, predictable velocity

44. What is continuous integration/delivery in an Agile context?

CI/CD is a technical practice that enables Agile's core promise of frequent delivery:

Without CI/CD, Agile teams accumulate integration risk and cannot truly deliver "potentially releasable" software every Sprint.

Advanced Questions

45. What is the difference between an Increment and a Release?

Modern teams aim to release continuously; the Increment enables this.

46. What is Timeboxing and why is it important in Scrum?

Timeboxing means events have a maximum duration that cannot be extended.

Scrum event time-boxes:

Why timeboxing matters:

• Ensures focus and urgency
• Prevents endless discussion
• Respects team time
• Creates rhythm and predictability

47. What is an Agile Release Train (ART) in SAFe?

An Agile Release Train is a long-lived team of Agile teams (50–125 people) that plans, commits, and executes together. Key properties:

• Trains on a common cadence — Program Increment (PI) of 8–12 weeks
• Shares a vision, roadmap, and backlog
• Produces a System Increment each PI
• Has a Release Train Engineer (RTE) as Scrum Master of the ART
• PI Planning aligns all teams, identifies cross-team dependencies

48. How do you handle a team member who doesn't follow Scrum practices?

1. Understand root cause — are they resistant to change, unclear on the framework, or facing genuine constraints?
2. Coach — have a 1:1 conversation; explain the purpose of the practice
3. Involve the team — at retrospective, discuss how the practice is working
4. Scrum Master responsibility — the SM must protect the framework while remaining servant-leader, not enforcer
5. Management — if the issue is systemic and obstructing the team, escalate to management with specific data
6. Never force — mandated compliance without understanding leads to lip-service Agile

49. What is Mob/Ensemble Programming and how does it relate to Agile?

Mob Programming (or Ensemble Programming): the whole team works together on one task at one computer simultaneously.

50. What are common Agile anti-patterns to avoid?

Agile vs Other Methodologies

Common Mistakes

Frequently Asked Questions

Q: Do you need to be certified in Scrum to work Agile?
No. Certifications (CSM, PSM, CSPO) demonstrate knowledge but are not required. Practical experience and understanding of the principles matter more.

Q: What's the difference between a Product Backlog and a Sprint Backlog?
The Product Backlog contains everything that might be needed in the product (owned by PO). The Sprint Backlog is the subset selected for the current Sprint, plus the team's plan for delivering it (owned by Developers).

Q: Can you run Scrum without a Scrum Master?
Technically yes, but the team typically struggles. The Scrum Master role prevents common dysfunctions: skipped events, ignored impediments, stakeholder interference, poor team dynamics.

Q: What is the difference between Agile and DevOps?
Agile focuses on how teams plan, develop, and deliver software iteratively. DevOps extends this to operations — continuous integration, delivery, deployment, and monitoring. DevOps enables Agile's promise of frequent, reliable releases.

Q: How do you handle a distributed/remote Agile team?

• Use video for all ceremonies (cameras on)
• Invest in digital tooling: Jira/Linear for backlog, Miro for collaboration, Slack for async communication
• Increase written communication clarity
• Consider overlapping core hours for key ceremonies
• Rotate Daily Scrum timing if spanning time zones

Q: What is the "cone of uncertainty" in Agile?
The cone of uncertainty describes how project estimates are most inaccurate at the beginning and become more accurate as work progresses. Agile embraces this by iterating and refining estimates continuously rather than making precise upfront commitments.