Scrum
312 bites tagged Scrum — interview questions with model answers, and 60-second explainers.
Why the Sprint is a 'container' for empiricism
A steady cadence creates regular inspection points, the Sprint Goal stays fixed once committed, and Developers are shielded from scope churn. that the fixed-length Sprint is what makes inspect-and-adapt possible.
Swap Velocity for PBI Count in Sprints
Scrum.org's Story Points Detox Plan swaps velocity for PBI count charts using existing sprint data. Teams often find item counts more stable for forecasting than story points.
Agile transformations die from dishonesty, not ceremonies
Agile transformations fail when teams perform perfect ceremonies while hiding hard truths in hallways, not from missing certifications. Leadership must make bad news safe to send upward. No framework fixes a culture that rewards appearances over outcomes.
Which Scrum event best diagnoses systemic failure to deliver a usable Increment?
Tests whether you distinguish process inspection from product inspection. Answer: Sprint Retrospective, because it plans quality and effectiveness improvements and adapts the Definition of Done. Red flag: naming Sprint Review or calling it a blame session.
Purpose of a shared Definition of Done for multi-team products
This tests empirical transparency across teams building one Increment. A shared DoD forces cross-team integration and testing before Sprint end. Letting teams keep separate DoDs hides integration debt and breaks transparency.
How do you adapt in-progress work when feedback invalidates a key assumption?
Alert the PO, renegotiate Backlog if the Goal is at risk, use feature flags to isolate invalidated logic. Empirical adaptation when assumptions fail. Deferring action to the next Sprint or changing scope alone.
Sprint Goals met but features don't solve stakeholder problems
Cite weak Product Goal alignment, shallow Review inspection, and missing outcome metrics. Distinguishing output from outcome in Sprint Review. Blaming stakeholders or pushing velocity instead of backlog adaptation.
A task takes longer than estimated, jeopardizing the Sprint Goal. Next steps?
This tests empirical adaptation when forecasts fail. Strong answer: inspect in the Daily Scrum, adapt scope with the Product Owner, and protect the Sprint Goal via self-management.
What strategy would you propose to fix an unmanageable backlog?
Expose bloat, inspect for value so the PO re-orders and trims waste, then inspect regularly. Do you see bloat as a transparency and ordering problem for the PO? Never let the team delete without the PO or treat the backlog as unordered.
How does a self-managing team resolve strong technical disagreements without escalation?
This tests if you see conflict as healthy creative tension. A strong answer covers timeboxed dialogue, multi-voting with reasoning, and the senior dev as neutral facilitator. A red flag is letting the senior dev dictate the answer or escalate to management.
Definition of Done: how does a shared DoD impact quality and predictability?
Increment is Sprint value; opaque states mislead inspection; shared standards create predictability. Linking Increment transparency to empirical inspection.
How do you navigate separating what from how with a prescriptive PO?
Tests Scrum's boundary: PO owns value and what; Developers own how. Strong answers reframe the user outcome, propose the simpler solution in Sprint Planning with tradeoffs, and preserve autonomy without overriding the PO. Red flag: blind obedience or defiance.
Sprint Review vs Retrospective: purpose, focus, and audience
Review inspects the Increment with stakeholders to adapt the backlog; Retrospective inspects process to improve ways of working. Distinguishing product and process inspection in Scrum. Treating both as the same meeting.
What is throughput and how does it differ from velocity?
Tests whether you know throughput is count-based and velocity estimate-based. Define throughput as items finished per sprint regardless of size, contrast velocity's point sum, pick throughput for forecasting and keep velocity for calibration.
How do you evolve a team from dependent to self-managing?
Tests situational leadership across Tuckman's stages. Answer: direct in Forming, facilitate conflict in Storming, observe in Norming, system-coach in Performing, and retire each stance as trust grows.
Manager wants to attend your Sprint Retrospective. Risk and response?
This tests your grasp of psychological safety in retrospectives. A strong answer cites the observer effect, proposes an alternative forum first, and sets ground rules if attendance is required.
What options exist when a story is too large for one sprint?
This tests vertical-slicing discipline versus architectural decomposition. A strong answer covers splitting by user value, checking INVEST criteria, and avoiding task-like layers. A red flag is proposing horizontal database or UI splits that defer feedback.
How should the team handle an oversized user story in Sprint Planning?
Split it vertically with the Product Owner, swarm the top slice, and renegotiate scope rather than overcommitting. Protecting the Sprint Goal when a story is too big. Proposing overtime or horizontal splits.
What structural impediments drive Zombie Scrum in agile transformations?
Spot project funding, component silos, absent real stakeholders, HR incentives that punish team autonomy, and a utilization culture killing improvement. diagnosing org design beyond team rituals.
How do you handle NFRs in the backlog and make them visible?
Write NFRs as measurable backlog items with acceptance criteria; embed in Definition of Done; decompose into tasks; automate validation. Making NFRs visible and actionable in Scrum.
How do blockers and impediments differ, and when do you escalate?
It tests whether you separate immediate task stops from chronic drag. Blockers are red-light stops for swarming; impediments are velocity drains surfaced in retrospectives and escalated with data.
How does an engineering manager's role change moving to agile autonomous teams?
Tests understanding of shifting from command-and-control to coaching and enabling teams. Strong answers cite three domains: team coaching, value investment, and environment shaping, plus servant leadership.
How do you spike a story to de-risk it and define deliverables?
Whether you see spikes as time-boxed research, not feature work. Propose a fixed duration, define the specific question, deliver a decision record or prototype, and revise the story estimate. Never treat a spike as production code or skip the time box.
What is the primary difference between Sprint Review and Sprint Retrospective?
Tests separation of product feedback from process improvement. Review: stakeholders inspect the Increment and adapt the backlog. Retrospective: Scrum Team only inspects its process and plans improvements. Red flag: calling either a status report or demo.
Get Scrum bites daily.
Five a day, five minutes, offline. With quizzes so it sticks.
Open testing — you’ll join as an early tester.