Sprint Review
Basic
difficulty
Stage 2
Agile IQ® Level
Empiricism
Practices
Scrum
Framework
Introduction
The Sprint Review is held on the last day of the Sprint to inspect the Increment and adapt the Product Backlog. During the event, the Scrum Team and stakeholders review what was accomplished in the Sprint and what has changed in their environment. Based on this information, attendees collaborate on what to do next. The Product Backlog may also be adjusted to meet new opportunities.
The Sprint Review is a working session and the Scrum Team should avoid limiting it to a presentation or a ‘demo’.
Timebox: 4 hours for a one-month Sprint. Less if your Sprints are shorter.
Don't just do a "demo"
Many teams do a demo or showcase of their work to stakeholders in the Sprint Review. While this is not a bad thing, it detracts from the real reason the Sprint Review exists: to get feedback from the current situation of delivery, and from stakeholders, to agree on what the next Sprint will look like.
Who should attend?
- Product Owner.
- Scrum Master.
- Developers.
- Stakeholders.
How do run an effective Sprint Review
Walk-through the Increments the team has created. These are items of work that have met the Definition of Done. If items have not met the Definition of Done, return these to the Product Backlog.
Elicit feedback from the team’s context, including:
- Do stakeholders have any feedback on the Increments they’ve just seen?
- Have stakeholder’s needs changed?
- Have any Agile KPI metrics moved since last Sprint Review, e.g. usage index, customer satisfaction, and what does this mean for investment in features or work for the next Sprint?
- Does the roadmap need to change based on this information?
- Does the budget need to change based on this information?
- What does next Sprint look like?
Download
Download the Sprint Review guide to print and use with your team.
References
1. Sutherland, J. and Schwaber, K. (2020). The Scrum Guide. The Definitive Guide to Scrum: The Rules of the Game.
All fields are required.
