The Sprint Review

  • Explain the purpose of the Sprint Review
  • Describe who attends and how it should be run
  • State the timebox and what can change as a result

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 its 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. It is the second-to-last event of the Sprint and is timeboxed to a maximum of four hours for a one-month Sprint, usually shorter for shorter Sprints.

Only work that meets the Definition of Done is part of the Increment, so only Done work is inspected as part of the Increment. Items that are not Done are not presented as complete; they go back to the Product Backlog for future consideration.

Study focus: the Sprint Review is not a sign-off gate or an approval meeting, and it is not the only moment value can be released — an Increment may be delivered to stakeholders before the end of the Sprint. Expect questions about collaboration with stakeholders and adapting the Product Backlog.

Key terms in this chapter

Sprint Review · Working session · Key stakeholders

Previous: The Daily Scrum · Next: The Sprint Retrospective

Try the free Scrum Master practice questions · Take the free Scrum Master mock exam