Scrum Guide
FAQ
← Back to FAQ

What Is a Sprint Review Meeting?

A sprint review meeting is the second last event of the Scrum sprint cycle where the Scrum master, product owner, development team, and stakeholders review the outcome and determine what can be closed off and what still needs work.

Why hold sprint review meetings?

The demonstration plays a central role in the sprint review meeting where the team, along with internal and external stakeholders, can have a  firsthand view of a working version of the product increment. The purpose of a sprint review meeting goes beyond the product experience, though. The product backlog is updated and budgeting, capacity, and timelines are reviewed too.

The goal of the sprint review meeting, instead, can be summarized this way: to inspect the product increment and adapt the product backlog.

Ultimately, it’s about reaching the end of the sprint having clear goals for the next one.

Running a sprint review meeting

Sprint review meetings can take anywhere from two to four hours and are typically held in person.

Here are items that you would typically see on a sprint review agenda

  • Welcome and housekeeping
  • Sprint status
  • Review of top requirements and key
  • Scrum metrics
  • Product demo
  • Review of user stories
  • Product backlog refinement
  • Closing

Complementing the agenda is a sprint review checklist featuring a more granular list of items relating to sprint’s work to assess and check off.

Running sprint review meetings online

With remote working becoming more widespread, teams are using online meeting platforms along with project management tools such as Wrike to provide sprint feedback.

An example of this would be Wrike’s integration with Microsoft Teams which extends collaboration and messaging to Team’s video conferencing capabilities.

Further reading