A Sprint Review is held at the end of the Sprint to inspect the Increment and adapt the Product Backlog if needed. During the Sprint Review, the Scrum Team and stakeholders collaborate about what was done in the Sprint. Based on that and any changes to the Product Backlog during the Sprint, attendees collaborate on the next things that could be done to optimize value. This is an informal meeting, not a status meeting, and the presentation of the Increment is intended to elicit feedback and foster collaboration.
This is at most a four-hour meeting for one-month Sprints. For shorter Sprints, the event is usually shorter. The Scrum Master ensures that the event takes place and that attendees understand its purpose. The Scrum Master teaches everyone involved to keep it within the time-box.
The Sprint Review includes the following elements:
- Attendees include the Scrum Team and key stakeholders invited by the Product Owner;
- The Product Owner explains what Product Backlog items have been “Done” and what has not been “Done”;
- The Development Team discusses what went well during the Sprint, what problems it ran into, and how those problems were solved;
- The Development Team demonstrates the work that it has “Done” and answers questions about the Increment;
- The Product Owner discusses the Product Backlog as it stands. He or she projects likely target and delivery dates based on progress to date (if needed);
- The entire group collaborates on what to do next, so that the Sprint Review provides valuable input to subsequent Sprint Planning;
- Review of how the marketplace or potential use of the product might have changed what is the most valuable thing to do next; and,
- Review of the timeline, budget, potential capabilities, and marketplace for the next anticipated releases of functionality or capability of the product.
The result of the Sprint Review is a revised Product Backlog that defines the probable Product Backlog items for the next Sprint. The Product Backlog may also be adjusted overall to meet new opportunities.
The What is Scrum Blog Series are excerpts from the Scrum Guide by Ken Schwaber and Jeff Sutherland. Offered for license under the Attribution Share-Alike license of Creative Commons, accessible at http://creativecommons.org/licenses/by-sa/4.0/legalcode and also described in summary form at http://creativecommons.org/licenses/by-sa/4.0/.
- An Introduction to Scrum
- What Are the 3 Pillars of Scrum?
- What are the 5 Scrum Values?
- What is a Scrum Team?
- What is a Scrum Product Owner?
- What is a Scrum Development Team?
- What is the Ideal Size of a Scrum Development Team?
- What is a Scrum Master?
- What are the Scrum Events?
- What is a Sprint?
- Who can cancel a Sprint?
- What is Sprint Planning?
- What is a Sprint Goal?
- What is a Daily Scrum?
- What is a Sprint Review?
- What is a Sprint Retrospective?
- What are the Scrum Artifacts?
- What is a Product Backlog?
- What is Product Backlog Refinement or Grooming?
- What is a Sprint Backlog?
- What is a Product Increment?
- What is a Definition of “Done”?
- Who is Monitoring Progress?
- The Importance of Artifact Transparency
- Scrum Foundations Course Video Series