Scrum
312 bites tagged Scrum — interview questions with model answers, and 60-second explainers.
How do you fix a Daily Scrum that runs too long?
This tests your understanding of the Daily Scrum's purpose (inspection, not problem-solving). A good answer involves re-educating the team, using a 'parking lot' for deep dives, and coaching individuals.
Who's accountable when an increment fails the user?
Tests your grasp of shared accountability in Scrum. A great answer avoids blame, highlighting the PO's role in value but also the whole team's duty to understand the 'why.' Propose concrete fixes like better backlog refinement.
How to handle a PO defining the technical implementation?
This tests your understanding of Scrum roles and ability to influence stakeholders. A great answer seeks to understand the PO's "why," presents alternatives with data, and reinforces shared goals and responsibilities. A red flag is being confrontational.
Handling Mid-Sprint Scope Change Requests
This tests your grasp of the Sprint Goal's immutability vs. the Sprint Backlog's flexibility. Acknowledge the PO's need, assess impact on the Sprint Goal, and negotiate trade-offs. If the goal is endangered, propose deferring or canceling the sprint.
Your Role in a Product Backlog Refinement Meeting
This tests your proactive role in Scrum beyond just coding. A great answer covers decomposing work, asking clarifying questions, estimating effort, and identifying technical risks.
What is the Definition of Ready for a backlog item?
Tests your grasp of upstream quality gates in Agile. Define DoR as a team's checklist for sprint-ready items, explain it protects dev focus and predictability, and give examples like clear acceptance criteria.
How do you handle an urgent, mid-sprint stakeholder request?
Tests your understanding of Scrum roles and stakeholder management. First, acknowledge the request's urgency. Then, redirect the stakeholder to the Product Owner, who manages all new work. A red flag is saying 'yes' and derailing the sprint, or a flat 'no'.
Scrum Empiricism: Retro and Definition of Done
This tests your grasp of Scrum theory beyond mechanics. A great answer links the Definition of Done to transparency, the Retrospective to inspection, and the Retro's output to adaptation. A red flag is confusing the Sprint Review with the Retrospective.
How does the Sprint container enable empiricism and protect developers?
This tests your grasp of the Sprint's structural role in Scrum. A good answer defines the Sprint as a fixed-length container for all events, explains how this cadence enables empiricism, and how the Sprint Goal protects developers.
How do you handle an urgent mid-sprint feature request?
This tests your understanding of Scrum roles and protecting the Sprint Goal. A great answer redirects the stakeholder to the Product Owner, who then assesses the request's impact and negotiates with the team if it can be swapped in without harming the Sprint…
How does a team forecast work for a Sprint?
This tests if you know the Developers own the forecast, not the PO or SM. A good answer cites past performance, current capacity, and the Product Backlog as inputs. A red flag is saying the Product Owner dictates the work.
Relationship Between Product Backlog, Sprint Backlog, and Increment
This tests your understanding of Scrum artifacts as commitments to goals, not just to-do lists. Define the Product Backlog (Product Goal), Sprint Backlog (Sprint Goal), and Increment (Definition of Done), then trace an item's flow.
What is the purpose of Sprint Review vs. Sprint Retrospective?
This tests your grasp of Scrum's distinct feedback loops. The Review inspects the product Increment with stakeholders to adapt the Product Backlog. The Retrospective inspects the team's process with the Scrum Team only.
Describe the purpose of the Daily Scrum
Tests if you know the Daily Scrum is a planning event for Developers, not a status report. A good answer states it's a 15-min meeting to inspect progress toward the Sprint Goal and adapt the Sprint Backlog.
What are the three Scrum accountabilities and their focus?
Tests recall of Scrum's core team structure and how the roles create a self-managing unit. A good answer names the Product Owner (value), Developers (Increment), and Scrum Master (process) and defines their focus.
Agile Change vs. Chaos: Technical Enablers
Tests if you know Agile is disciplined, not chaotic. A great answer contrasts structured, time-boxed change with reactive chaos, then details technical enablers like CI/CD and loose coupling. A red flag is equating Agile with no planning.
Explain Muda (Waste) with three software development examples
Tests your ability to apply Lean's 'Muda' (waste) concept to software. A good answer defines Muda, then gives 3 examples like partially done work or extra features, with specific mitigations like WIP limits or YAGNI. A red flag is giving generic examples.
Explain the Agile principle of Simplicity and how you apply it.
This tests your ability to connect Agile theory to engineering practice. A good answer defines simplicity as maximizing work not done, applies YAGNI with a concrete example (e.g., phased feature rollout), and links it to business value.
Goal of a Retrospective and Continuous Improvement
Tests if you see process improvement as a core engineering duty. A great answer defines the retro's goal (inspect & adapt the process), its output (actionable items for the next Sprint), and its role as the engine of continuous improvement.
Individuals & Interactions Over Processes & Tools: Explain This Value
Tests your grasp of Agile's core philosophy: empowering people over rigid systems. A great answer defines the principle, links it to cross-functional team structures, and champions direct communication over ticket-passing.
AI Turns Specs Into a Programming Language
Spec-Driven Development (SDD) reframes specs as a higher-level programming language for AI agents, not just pre-coding docs. This shifts engineering work from implementation details to defining intent and constraints.
Scrum.org's 8-Step Plan for AI-Native Teams
Scrum.org has outlined an 8-step framework to guide teams in becoming 'AI-native.' This structured approach aims to embed AI into all aspects of Scrum, shifting focus from production to evaluation and from 'Definition of Done' to 'Definition of Value'.
Make Agile Planning a Shared Problem
Chaotic sprints and messy backlogs often result from planning being treated as a solo task. This siloed approach leads to overcommitment and erodes stakeholder trust, making agile feel unreliable.
Mountain Goat Software Ends Public Agile, Scrum Classes
Mountain Goat Software is ending its public Agile/Scrum courses to focus on private team training. This removes a key option for individual certification, forcing engineers to find alternatives or convince managers to book a more costly private session for…
Get Scrum bites daily.
Five a day, five minutes, offline. With quizzes so it sticks.
Open testing — you’ll join as an early tester.