“held at the end of the Sprint to inspect the Increment and adapt the Product Backlog if needed” (1)
Overview
Definition: a formal event to inspect the increment and collaborate on the next things to optimise value
Length: 4 hours for a month long Sprint. For shorter Sprints the event is usually shorter.
Inputs: Product Increment (which must adhere to the Definition of Done), Product Backlog, Impediments that Stakeholders can help resolve
Outcome: Product Increment, Feedback on Product Increment adapted in the Product Backlog, updated impediments
People: Product Owner, Scrum Master, Development Team, Stakeholders (by invitation from the Product Owner)
Sprint Review Contents
The Sprint Review includes the following elements (1)
- 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
- Review of the timeline, budget, potential capabilities, and marketplace for the next anticipated releases of functionality or capability of the product
Sprint Review Agenda (2, page 37)
- Product Owner reviews the planned Sprint Goal and what has been accomplished
- The Scrum Team inspects the Product Increment with Stakeholders by discussing the approach they took, reviewing the challenges and their resolutions, and inspecting the Product Increment
- The Product Owner discusses the Product Backlog and likely completion date
- The Scrum Team and Stakeholders collaborate by determining what to build in the upcoming Sprint
Sprint Review Agenda (3, page 182)
- Explanation of the PO’s vision for the product
- Review of the release plan and budget
- Description of the Sprint Goal for this sprint
- Review of the work and the product increment that the team built
- Assessment of current customer analytics and data
- Discussion of impediments the team is currently facing
- Collaborating with stakeholders to refine the Product Backlog
- Summary of where we’re going next and what we discovered in this event
Techniques
Sprint Review Smells
Sprint Review Smells (2, page 38)
- There isn’t anything to show at the Sprint Review so it is cancelled
- It is a mandatory event so cannot be cancelled
- Opportunity for inspection and adaption should not be missed
- Feedback from Stakeholders helps to determine the direction for the next Sprint
See also
References
- The Scrum Guide
- Scrum Insights for Practitionersby Hiren Doshi
- Fixing Your Scrum by Ryan Ripley and Todd Miller
Explore Other Scrum Events
 |  |  |  |
3 thoughts on “Sprint Review”