The Scrum Guide – 2020
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.
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.
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.
© 2020 Ken Schwaber and Jeff Sutherland
Commentary
In the ‘pre-Scrum Guide’ era, Scrum practitioners called this event a “demo”. The review is a more generic term, with a broader agenda. However, as we can see in the detailed list of its elements, it still includes the demonstration. The changes in the Scrum Guide between 2011 and 2013 made it even clearer that the scope of the Sprint Review should be broader than demo+feedback.
People associate organizing and facilitating Scrum meetings with the role of the Scrum Master, but the Scrum Guide does not prescribe this. The Scrum Master may organize this event if that fits best the team’s situation, however, a self-managing team may decide otherwise. What is more, according to the 2017 version of the Guide, it was the Product Owner’s responsibility to invite the key stakeholders. It does not mean the Scrum Master is not accountable for the quality of this event, though.
Note, that as per the Guide, the Sprint Review is an informal meeting, not a status meeting. Project-focused organizations may tend to hijack the Sprint Review and use this meeting for reporting.
Practical Considerations for Organizing the Sprint Review
Typically no, the Sprint Review is typically shorter than 4 hours and should have a practical agenda, guiding the stakeholder if and when to participate.
It is better to have a list of findings that may interest the stakeholders and discuss the rest elsewhere.
Strictly based on Scrum events the Product Owner would face the up-to-date status right at the meeting, surrounded by the key stakeholders. The Scrum Guide does not detail when the Product Owner should first see the “Done” backlog items and when should those get approved. It is up to the team.
From a practical point of view, the Product Owner is the best person to invite the stakeholders, but this is not a rule.
From a practical point of view, the Product Owner is the best person to invite the stakeholders, but this is not a rule.
For the above reasons, it is typical that teams hold a short preparation meeting before the Sprint Review. They discuss the agenda, the list of invitees and the status of the Sprint. If the demonstration is part of the Review, they have to prepare an environment or system that is appropriate for the purpose.
Holding a demonstration can be highly beneficial, however, that is not the single ultimate goal of this event! The outcome of the Sprint Review is one of the important inputs of Sprint Planning.
Key Takeaways
- The Sprint Review is an informal meeting of the Scrum Team and the stakeholders.
- The Sprint Review is not just a demo, the participants discuss the state of the product and the direction to go.
- The Sprint Review is an opportunity for inspection and adaptation.
- There is no rule on who should facilitate the meeting or demonstrate the improvements.
External content: Scrum.org’s YouTube video about facilitating Sprint Review
The Scrum Guide – 2017
Sprint Review
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.
©2017 Ken Schwaber and Jeff Sutherland.
The Scrum Guide – 2010
Sprint Review
At the end of the Sprint, a Sprint Review meeting is held. This is a four hour time-boxed meeting for one month Sprints. For Sprints of lesser duration, allocate proportionately less of the total Sprint length to this meeting (for example, two weeks would be a two-hour Sprint Review). During the Sprint Review, the Scrum Team and stakeholders collaborate about what was just done. Based on that and changes to the Product Backlog during the Sprint, they collaborate about what are the next things that could be done. This is an informal meeting, with the presentation of the functionality intended to foster collaboration about what to do next.
The meeting includes at least the following elements. The Product Owner identifies what has been done and what hasn’t been done. The Team discusses what went well during the Sprint and what problems it ran into, and how it solved these problems. The Team then demonstrates the work that is done and answers questions. The Product Owner then discusses the Product Backlog as it stands. He or she projects likely completion dates with various velocity assumptions. The entire group then collaborates about what it has seen and what this means regarding what to do next. The Sprint Review provides valuable input to subsequent Sprint Planning meeting.
© 2008-2010 Ken Schwaber and Jeff Sutherland, All Rights Reserved