Sprint Review is a Scrum Event that summarizes the work on the Product that was completed during the current Sprint. It takes place on the last day of the Sprint and is open to Stakeholders. Its purpose is to evaluate the Increment, i.e. to present the latest version of the Product. An important part of the Sprint Review is also the discussion of the improvements and updates made. And also to make the necessary changes to the Product Backlog, so that all Stakeholders can see the current status of the Product.

Sprint Review – table of contents:

  1. Introduction
  2. The role of Stakeholders during Sprint Review
  3. Releasing Increments
  4. Working on the Product Backlog during Sprint Review
  5. Summary


Sprint Review and Sprint Retrospective are two Sprint Summary Events. In this article we wrote more extensively about the roles that each Scrum Event plays. Today, we’ll just mention that they provide an opportunity to ground the three pillars of empiricism – transparency, inspection, and adaptation – concerning the Product and the work of the Scrum Team.

Sprint Review is dedicated to the Product. And its purpose is to inspect the Increment, i.e. the results of the work done in the Sprint that just ended. The event lasts a maximum of four hours. All members of the Scrum Team, as well as Stakeholders, i.e. all people interested in the progress of the Product attend it.

The role of Stakeholders during Sprint Review

During the Sprint Review, the Scrum Team presents the Increment to the Stakeholders. In doing so, it summarizes the completed tasks and answers specific questions:

  1. Who performed the task?
  2. What specifically was done?
  3. For what purpose was it done?
Sprint Review

The Stakeholders provide feedback to the Scrum Team members. This allows for adaptation, i.e. adjusting the Scrum Team’s way of working to the needs and vision of the Customer. This is done to maximize the business value of the Product. The feedback provided at each Sprint Review is particularly important when creating innovative products that need to be adapted on an ongoing basis to the activities of the competition and the needs of the market.

Releasing Increments

We shouldn’t consider Sprint Review as the only time the Scrum Team releases an Increment to the Customer. If some Product functionality meets the Definition of Done beforehand, the Product Owner may decide to release it immediately.

It is also possible that an item of the Product Backlog that the Scrum Team worked on in a given Sprint has not been completed and does not meet the Definition of Done. It cannot then get released or even presented during Sprint Review.

Working on the Product Backlog during Sprint Review

Updating the Product Backlog is as much a part of Sprint Review as presenting the work results to Stakeholders. Usually, the Backlog update is dedicated to the last part of the meeting, so Stakeholders do not have to attend.

The Product Owner updates the Product Backlog based on feedback from Stakeholders and lessons learned by the Development Team. This is especially crucial if the feedback obtained has an impact on the shape and Purpose of the next Sprint. Updating the Backlog is then an essential step to preparing the next Sprint Planning.

sprint review

Sprint Review – summary

Sprint Review is a meeting of the Scrum Team with Stakeholders, during which the results of the Product work obtained in the last Sprint are presented. Its key part is a discussion with Stakeholders, during which they give feedback on the Product. Thanks to this conversation, it is possible to effectively adapt and possibly correct the direction of work on the Product following market requirements. Thanks to the discussions with Stakeholders held at the end of each Sprint, the chances of maximizing the business value of the Product developed by the Scrum Team increase.

If you like our content, join our busy bees community on Facebook, Twitter, LinkedIn, Instagram, YouTube, Pinterest.

Scrum Guide | 37. Sprint Review caroline becker avatar 1background

Author: Caroline Becker

As a Project Manager, Caroline is an expert in finding new methods to design the best workflows and optimize processes. Her organizational skills and ability to work under time pressure make her the best person to turn complicated projects into reality.

Scrum Guide:

  1. Glossary of basic terms, roles and notions
  2. What is Scrum?
  3. Scrum values
  4. How to implement Scrum in your company?
  5. Scrum Team - what is it and how does it work?
  6. Who is a Product Owner?
  7. The most common mistakes of Product Owner
  8. Who is the Scrum Master?
  9. Characteristics of a good Scrum Master
  10. The most common mistakes of Scrum Master
  11. What statistics and metrics should the Scrum Master track?
  12. Cooperation between Product Owner and Scrum Master
  13. Development Team in Scrum
  14. The most common mistakes of Developers
  15. Scrum artifacts
  16. Scaling Scrum
  17. Sprint Backlog
  18. What is the Product Backlog?
  19. What are User Stories?
  20. Creating the best User Story with INVEST
  21. The most common User Story mistakes
  22. User Story Acceptance Criteria
  23. Estimation and Story Points in Scrum
  24. Planning Poker
  25. Team Estimation Game
  26. Defining Increment
  27. Scrum events
  28. What is Sprint in Scrum?
  29. Scrum Team Commitments - Product Goal, Sprint Goal and Definition of Completion
  30. What is a Burndown Chart?
  31. How to create and interpret a burndown chart?
  32. Advantages and disadvantages of the burndown chart
  33. Kanban boards in Scrum and Scrumban
  34. Velocity in Scrum - Speed of the Development Team
  35. Daily Scrum
  36. Sprint Planning
  37. Sprint Review
  38. What is a Sprint Retrospective?
  39. Common mistakes during a Sprint Retrospective
  40. Product Backlog nurturing