Read this post in: de_DEes_ESfr_FRhi_INid_IDjapl_PLpt_PTru_RUvizh_CNzh_TW

Scrum: What Is a Sprint Review?

The Sprint Review is an informal meeting where the development team, Scrum Master, Product Owner, and stakeholders come together. The team presents the product and determines what has been completed and what remains unfinished. The purpose of the Sprint Review meeting is to allow the team to demonstrate their work completed during the Sprint to customers and stakeholders, comparing it to the commitments made at the beginning of the Sprint.

Sprint Review vs. Sprint Retrospective

Each Sprint concludes with two key meetings: the Sprint Review and the Sprint Retrospective. The Sprint Review begins with a customer review and demonstration, and ends with the team retrospective. Both meetings occur on the final day of the Sprint.
The Sprint Review focuses on “Inspecting” and “Adapting” the Increment (potentially shippable product), while the Sprint Retrospective focuses more on “Inspecting” and “Adapting” the Sprint process itself.
Sprint Review vs. Sprint Retrospective
Sprint Review vs. Sprint Retrospective

Sprint Review of the Increment

In an Scrum team, the customer is invited to review and verify whether the work (potentially shippable increment) meets the Definition of Done at this point. Sometimes, customers may want to conduct acceptance testing before using the application. The goal of the meeting is to transparently review and determine the status of the work achieved during the Sprint:
  • Completed work
  • Work not yet completed
  • Work added
  • And work removed from the Sprint
It provides time for questions, observations, feedback, and suggestions, and discusses how to best move forward given the current reality.

Duration of the Sprint Review

The Sprint Review may last up to 4 hours for a 4-week Sprint. The general rule is that the Sprint Review should not exceed one hour per week of Sprint duration. The table below illustrates this rule:
Total Sprint Duration Sprint Review Duration
1 week 1 hour
2 weeks 2 hours
3 weeks 3 hours
4 weeks 4 hours

Sprint Review Meeting Template

There are many ways to conduct a Sprint Review. The following agenda outlines typical activities in a Sprint Review meeting:
  1. Start – The Sprint Review meeting begins.
  2. Welcome Stakeholders – The Product Owner welcomes stakeholders to the review.
  3. Current Review Agenda – The Product Owner presents the agenda for the Sprint Review.
  4. Current Product Increment – The development team demonstrates the product increment implemented during the Sprint.
  5. Collect Feedback – The Product Owner requests feedback from stakeholders on the delivered product.
  6. Current Product Backlog – The Product Owner presents the top of the Product Backlog to stakeholders, seeking feedback on upcoming Sprint items and gathering stakeholder input on backlog priorities.
  7. Meeting Concludes