Your browser does not support JavaScript! Sprint Review - Scrum Inc.
  • LinkedIn
  • YouTube
  • RSS

Sprint Review

The Sprint Review takes place at the end of the Sprint and is designed to gather actionable feedback on what the Team has completed. This ceremony, also known as the "Demo", is an exciting opportunity for the team to showcase its work and to inspect the overall roadmap for the product (Product Backlog).

Estimated time for this course: 5 minutes
Audience: Beginner
Suggested Prerequisites: Scrum Framework, Potentially Shippable Product

Upon completion you will:

  • Understand the purpose of the Review
  • Know the history of the first review
  • Have learned about the importance of having working product
  • Learn who attends the review
  • Qualify for Scrum Alliance SEUs and PMI PDUs. See FAQ for details
Sprint Review Overview:
The purpose of the demonstration is to produce a conversation between the Team and the stakeholders about how to make the product better. The Product Owner incorporates the lessons learned during the conversation into the Product Backlog, completing yet another inspect and adapt cycle. The meeting itself should be strictly time boxed to no more than an hour per week of Sprint. (So a two-week Sprint would have a two-hour review and a one-week sprint a one-hour review.)

Another important, but often overlooked aspect of the review is to have working software. The point of the review is to get feedback from the customer and end user. If the software isn't tested and working then its not possible to start this important feedback loop. Remember, the review does include a demonstration, but the focus should be a conversation. In the video Jeff explains how this ceremony came about.

View Class Slide

 [slideshow_deploy id='5126']

Elements of the Review
  • 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 completion 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 nextanticipated release of the product.

The Scrum Guide