The Sprint Review cover image
Product Management

The Sprint Review

Optimize value and transparency with effective Sprint Reviews in your Scrum process.

Sjoerd Nijland
Nov 22, 2018 • 10 min read
-
Intermediate
Encouraging Participation
Feedback Sessions
Organizational Learning
Outcome Focus
Self-organization
Show More

Summary

This article explores the purpose and execution of the Sprint Review within the Scrum framework, emphasizing its role in optimizing value and enhancing transparency between the Scrum Team and stakeholders. It details the importance of feedback, the involvement of stakeholders, and the iterative nature of product development. Key challenges such as stakeholder participation and the necessity of open communication are addressed. The article encourages Scrum Teams to embrace transparency and adaptability to improve their processes continuously.

Takeaways

  • Preparation and alignment on feedback and next steps are essential for a successful Sprint Review.
  • Stakeholder participation is crucial for the success of the Sprint Review.
  • The Sprint Review is not just a status update but an opportunity for feedback and collaboration.
  • The Sprint Review should be held regardless of whether all Sprint Goals are achieved.
  • Transparency and open communication are key to addressing challenges during the Sprint Review.
  • A Sprint Review is an informal meeting, not a status meeting, where the product increment is presented to elicit feedback and foster collaboration.
  • A Sprint Review is held at the end of the Sprint prior to the Sprint Retrospective and should take at most 4 hours.
  • The Scrum team and the Scrum masters should self-organize a material that includes the refined product backlog, the sprint goal, the definition of Done, etc. when preparing for the Sprint Review.
  • The goal of the Sprint Review is to inspect the increment and adapt the product backlog if needed to optimize value.

Suggested Resources