Sprint Review
A Scrum ceremony held at the end of each Sprint where the team demonstrates the working increment to stakeholders and collects feedback. Unlike a status report, the Sprint Review is a collaborative working session — stakeholders inspect what was built, ask questions, and influence the product backlog based on what they see.
How to run it
- 1
Open with a brief recap of the Sprint Goal and what was committed to.
- 2
The development team demonstrates the working increment — only completed, 'Done' features. No slideware, no mock-ups.
- 3
Stakeholders ask questions, try the product, and give feedback in real time.
- 4
The Product Owner explains what has been accepted as Done and what wasn't completed, and why.
- 5
Review the Product Backlog together: given what was learned today, what should be prioritised next?
- 6
Close with an updated forecast for the next Sprint and any adjustments to the product roadmap.
Tips
The Sprint Review is not a formal sign-off meeting — it's a conversation. Keep it collaborative.
Only show working software. Demonstrating incomplete features erodes trust.
Invite real users, not just internal stakeholders, whenever possible — their feedback is more valuable.
Timebox strictly: 1 hour per week of Sprint length (max 4 hours for a month-long Sprint).
Variations
Remote Sprint Review: use screen share + a Miro board where stakeholders drop sticky notes as they watch the demo. Async variant: record a Loom demo, collect written feedback via form, then hold a 30-min discussion session.
Where it fits
Related methods
Plan your next workshop with AI
Workshop Weaver helps you combine methods like Sprint Review into a complete, timed agenda in minutes.
Try it freeMethod descriptions on Workshop Weaver are original content written by our team, based on established facilitation practices. This method was inspired by work from Scrum Guide.