The Sprint Review is one of the five official Scrum events. It takes place at the end of each Sprint – after the Increment is completed and before the Sprint Retrospective. Its purpose is to inspect the outcome and adapt the direction: the Scrum Team and invited stakeholders review the Product Increment (only items that meet the Definition of Done), discuss what has changed in the environment, and collaboratively adapt the Product Backlog. The Sprint Review is a working session, not a status meeting or formal acceptance gate.
Timebox, Participants, Output
· Timebox: Up to 4 hours for a one-month Sprint; shorter for shorter Sprints.
· Participants: The entire Scrum Team (Product Owner, Scrum Master, Developers) plus relevant stakeholderssuch as customers, business owners, compliance, support, sales, or operations.
· Output: An adapted Product Backlog (with new items, reprioritized work, and updated forecasts) and, where relevant, initial hypotheses for future Sprint Goals.
Official Focus (Scrum Guide)
· Inspect the Increment: Only “Done” items, ideally shown as a live demonstration.
· Reflect on the Sprint Goal: Whether it was achieved and why.
· Review changes in the environment: Market shifts, customer feedback, regulatory or technical changes.
· Adapt the Product Backlog: Update priorities and forecasts toward the Product Goal.
· Collaborate actively: Stakeholders and Scrum Team shape the future direction together.
Deep-Dive: Typical Agenda Elements for Experts
· Context & Goal: Revisit Product Goal and Sprint Goal; link to strategy or OKRs.
· Increment Walkthrough: Show end-to-end user flows instead of isolated features.
· Outcomes & Evidence: Present product metrics (activation, funnel drop-offs, time-to-value), telemetry, user feedback, or research insights.
· Risks & Decisions: What is validated, what remains a hypothesis, and which decisions are pending.
· Backlog Adaptation live: Create or adjust PBIs in real time, including acceptance criteria and assumptions.
· Forecasting (lightweight): Provide directional expectations without commitments, based on past throughput and dependencies.
Scaling: Multiple Teams, One Product
When several Scrum Teams work on the same product, they present one integrated Increment:
· Joint Review: Coordinated session with team-specific segments but a consistent product story.
· Technical enablers: Show architecture runway or platform capabilities when they enable future value.
· Stakeholder routing: Structure the agenda for different groups (e.g., business impact first, technical details later).
· Backlog clarity: Maintain one Product Backlog and one Product Goal, not competing artifacts.
Good Practices (Field-Tested, not in the Scrum Guide)
· No slide decks: Use live systems, staging environments, or prototypes instead of PowerPoint.
· Focus on outcomes: Demonstrate impact, not just completed tickets.
· Review Canvas: A one-page summary with goal, key insights, metrics, risks, backlog changes, and next hypotheses.
· Invite real users: Customer representatives or proxies (support, sales engineers) can provide valuable feedback.
· Include compliance & ops early: Integrate regulatory, security, or operations perspectives to reduce friction later.
· Remote-friendly setups: Short time-boxed slots, cameras on, technical dry-runs, and real-time backlog updates.
Common Misconceptions
· “The Review is an acceptance meeting.” False – it is about feedback and direction, not formal approval.
· “Only Developers present.” In fact, it is a collaborative workshop with full Scrum Team and stakeholders.
· “The PO alone updates the backlog.” Backlog adaptation is a joint effort during the Review.
Practical Relevance in Transformations
The Sprint Review is a critical feedback loop. It anchors customer orientation and prevents months of misaligned development. In large organizations, it becomes a strategic alignment forum, ensuring that strategy and execution stay synchronized and responsive.
CALADE Perspective
In many companies, Reviews are either too narrow (a simple demo) or too broad (a status show). CALADE supports teams in turning Reviews into strategic decision forums: with clear product storytelling, outcome evidence, focused stakeholder participation, and real-time backlog adaptation. Our coaches train Product Owners and Scrum Masters in advanced facilitation, stakeholder orchestration, and meaningful metric use – making the Sprint Review a heartbeat for direction and impact.
Related Terms
· Sprint
· Sprint Retrospective
· Product Owner
· Definition of Done
· Product Goal
← back to list