LEARN. PRACTICE. GROW.Concept and mechanism
Sprint Review is a working session for inspecting the Sprint outcome and discussing future adaptations. Showing features may help, but a demonstration monologue does not replace discussion of context, change, and value. Stakeholders bring needs and evidence the Product Owner can use to order work. Not every request must be accepted. Explaining criteria and consequences helps maintain trust even with competing priorities. The Retrospective has a different purpose: improving the quality and effectiveness of working practices.
Guided application
Invite operators who perform the task, product stakeholders, and other people relevant to the outcome under inspection. Prepare evidence and allow exploration of the usable increment. A change request may reveal a need different from the initial assumption. Confirm that need before choosing a solution. If two groups have opposite outcomes, investigate segments, context, and consequences; an average can hide important failures. After discussion, expose what changed in the backlog and what still needs investigation. A meeting without decisions or new hypotheses may not be using the inspection opportunity well.
The dashboard reduces work for one team and increases it for another. Review identifies process differences before deciding on expansion.
Common pitfalls
Inviting only budget approvers; promising to accept every request; ignoring unfavorable feedback.
Related topics: Value, vision, and Product Goal · Ordering, refinement, and investment decisions
Useful feedback should influence product hypotheses and choices.
Reference: The Scrum Guide, November 2020 · PSPO I; Scrum Guide November 2020; no public numbered exam revision