GuideRolesEventsWorkflow

Scrum Events

Sprint Review

The Sprint Review is where the Scrum Team presents the results of their work to key stakeholders and progress toward the Product Goal is discussed. It’s a working session — not a presentation or demo theater. The goal is to generate genuine feedback that informs what the team does next.

Inspecting the Increment · Timebox: ≤ 4 hours (1-month Sprint)

Overview

The Sprint Review is where the Scrum Team presents the results of their work to key stakeholders and progress toward the Product Goal is discussed. It’s a working session — not a presentation or demo theater. The goal is to generate genuine feedback that informs what the team does next.

Event Ownership

Owned / Facilitated By
Product Owner (content owner) / Scrum Master (facilitator)
Product Owner frames the session around the Product Goal and Sprint Goal outcomes
Product Owner facilitates the conversation about what to do next based on feedback
Scrum Master ensures the event is productive, inclusive, and stays within the timebox
Scrum Master helps create an environment where stakeholders give honest feedback

Who Should Be Present

Scrum Team (all)
Present the work accomplished, explain what was done and not done, and answer stakeholder questions
Product Owner
Opens the session with context on the Sprint Goal, leads discussion on backlog adjustments, and gathers feedback
Key Stakeholders
Provide feedback on the Increment, share market/business context changes, and collaborate on next steps
Scrum Master
Facilitates the session, ensures stakeholder voices are heard, and prevents the event from becoming a one-way presentation

Preparation Checklist

01Developers: Ensure the Increment is working, deployed to a reviewable environment, and meets the Definition of Done
02Product Owner: Prepare context on the Sprint Goal, what was completed vs. not, and upcoming Product Backlog direction
03Scrum Master: Invite the right stakeholders, prepare the room/tooling, and plan facilitation for interactive discussion
04Team: Prepare a live demo environment — avoid slide decks showing screenshots when you can show the real product

Facilitation Techniques

Click any technique to expand details and learn when to apply it.

Show, Don’t Tell

Demo the working Increment in a realistic environment. Let stakeholders interact with it directly when possible. Avoid slideshows that show what was built — let the product speak for itself.

Click to expand

Marketplace / Science Fair Format

Set up stations where different features or capabilities can be explored. Stakeholders rotate between stations, providing feedback directly to the Developers who built each piece. Great for larger groups.

Click to expand

What-If Scenarios

After showing the Increment, pose ‘What if’ questions to stakeholders: ‘What if we extended this to handle X? What if we invested more in Y?’ This generates richer feedback than ‘What do you think?’

Click to expand

Feedback Capture Grid

Use a 2×2 grid: Likes / Wishes / Questions / Ideas. Stakeholders place sticky notes in each quadrant. This structures feedback and ensures you capture both positive signals and constructive input.

Click to expand

Product Goal Progress Update

Open with a visual showing progress toward the Product Goal (a roadmap, a burnup, or a simple percentage). This grounds individual Sprint outcomes in the larger narrative and helps stakeholders see momentum.

Click to expand

Stakeholder Q&A Rounds

Instead of open-floor questions, do structured rounds: First round asks ‘What surprised you?’ Second round asks ‘What concerns you?’ Third round asks ‘What should we do next?’ This prevents dominant voices from monopolizing.

Click to expand

Tips & Tricks

01
This is a working session, not a presentation. If stakeholders are just watching, you’re doing it wrong
02
Show what was NOT completed too — transparency builds trust far more than hiding shortfalls
03
Invite the right stakeholders — too few means missing perspectives; too many means chaos
04
Have Developers demo their own work — it builds pride and connects stakeholders directly to the builders
05
Capture feedback in real-time where everyone can see it — don’t let insights disappear
06
End by confirming what feedback will be acted on and how it will be prioritized

Success Takeaways by Role

What each participant should walk away with when this event is run well.

Developers

Validation that their work matters; direct connection to user/stakeholder needs; pride in what they’ve built

Product Owner

Rich feedback to inform backlog ordering; stakeholder alignment on product direction; data for next Sprint Planning

Scrum Master

Observations on stakeholder-team relationship health; ideas for improving transparency and delivery

Stakeholders

Confidence in the team’s progress; influence on product direction; understanding of trade-offs and constraints

Cross-Framework Definition
See Sprint Review in the glossary
→