Scrum Guide
FAQ
← Back to FAQ

What Is the Goal of the Sprint Review Meeting?

To quote the official Scrum Guide, the purpose of sprint review “is to inspect the outcome of the Sprint and determine future adaptations.”

On a practical level, certain items on a sprint review checklist need to be addressed in order to assess whether the criteria for achieving the sprint goal have been met.

  • Product demonstration: To showcase completed functionality to the team, stakeholders, and gather feedback
  • Closure of completed user stories: Learning from the process and celebrating achievements
  • Review and re-prioritization of incomplete user stories: They can be added back to the product backlog or tackled in the next sprint
  • Update of the product backlog: In preparation for planning the next sprint

The goal of a sprint review meeting

Once tasks have been completed the sprint review’s goal is achieved: the product increment is inspected and the product backlog is adapted. This also means that, from a product perspective, the sprint is closed off and everything is ready to start the next one.

Sprint review meetings should also note processes-related points to address in the sprint retrospective meeting.

What happens if sprint goals are not achieved?

Typical scenarios include:

  • The increment is not quite ready or presentable
  • Not everyone can participate
  • The sprint goal has not been achieved

This is not uncommon and often sprint reviews are postponed until goals are achieved.

Further reading
article

How to Run a Scrum Meeting

blog post

How to Organize Goals and Milestones in Wrike