Sprint Review
Basic
difficulty
Stage 2
Agile IQ® Level
4:00h
Timebox
Sprint Review
EVENT
Introduction
The purpose of the Sprint Review is to inspect the outcome of the Sprint and determine future adaptations. The Scrum Team presents the results of their work to key stakeholders and progress toward the Product Goal is discussed.
Sprint Planning addresses three topics:
- Topic One: Why is the Sprint valuable?
- Topic Two: What can be Done this Sprint?
- Topic Three: How will the chosen work get done?
Review the Sprint
During the event, the Scrum Team and stakeholders review what was accomplished in the Sprint and what has changed in their environment.
Artefacts to Inspect
Key artefacts to inspect and review during this event are:
- The Increment of work – As soon as work achieves the Definition of Done it is considered an Increment. Work that hasn’t achieved Done should not be brought to this event. It should be returned to the Product Backlog. The Product Owner will decide whether or not work not Done is still of value to continue with next Sprint.
Artefacts to Adapt
Key artefacts to adapt and rearrange during this event are:
- Product Backlog – Any feedback is documented and put into the Product Backlog.
Elements to Review
Reviewing and discovering what has changed in the stakeholders and the product environment often includes:
- Metrics – Discuss what metrics, such as customer satisfaction, usage index, market trends, tell us about what customers and users might need or want now.
- Progress toward the Product Goal – What do the metrics say about the product goal? Is more investment needed to create the impacts the product is trying to make in the market or the outcomes its delivering for stakeholders?
- How users are using the product or service – What does usage tell us about how we might prioritise work for next Sprint?
- Forecasts, budget and milestones – If things have changed, what is the impact on any original plans?
- User Research – has user research given us any new insights into users’ motivations, wants, needs, or behaviours? Does this impact what we might do in future Sprints?
ADAPT THE PRODUCT BACKLOG FROM THE FEEDBACK
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.
The Sprint Review is the second to last event of the Sprint and is timeboxed to a maximum of four hours for a one-month Sprint. For shorter Sprints, the event is usually shorter, e.g. 2 hours for a 2-week Sprint.
Download
Download the Sprint Review checklist (PDF) to help you navigate this event.
References
1. Sutherland, J. and Schwaber, K. (2020). The Scrum Guide. The Definitive Guide to Scrum: The Rules of the Game.
