Skip to main content

The Purpose of the Sprint Review

September 8, 2020
Photo by Rachel Forrez - https://unsplash.com/@rachelforrez
Photo https://unsplash.com/@rachelforrez

 

Imagine you want to have a book written. You find a good author and have many discussions with him about the subject, ensuring he understands what should and shouldn't be included. Once the author has enough information, he begins writing, and after a year and a half, the book is finished. However, when you start reading, you discover numerous inaccuracies. Consequently, large portions of the book need to be rewritten. In such a situation, wouldn't you prefer to meet with the author every two weeks to review his progress? This way, you could correct him if needed, providing guidance along the way.

This is precisely why Scrum includes a Sprint Review at the end of every Sprint: it provides stakeholders with the opportunity to review and influence the product's development regularly.

The Sprint Review is not merely a "Demo" or a presentation. It is a collaborative event where the Scrum Team interacts with business stakeholders. During this event, the Scrum Team demonstrates what they have been working on during the past Sprint. Stakeholder involvement is highly valued by both the Product Owner and the Development Team, as it helps them make informed decisions about future work and provides valuable business insights, including context, background, challenges, methods, and needs.

While it is beneficial when the business is pleased with the solutions presented, the team also values hearing other perspectives, even if they are less positive. If stakeholders disagree with the prioritisation of items on the Product Backlog, this is the perfect time to voice those concerns. The Sprint Review allows stakeholders to be critical and express their views, fostering a collective discussion with all involved parties. This collaborative environment enables the team and stakeholders to make decisions together without the need for separate meetings, achieving the best results for the organisation. The business identifies opportunities, problems, and needs, while the Scrum Team commits to finding the best possible solutions.

So, the next time you are invited to a Sprint Review, don't ignore it. Attend and help the Scrum Team help you.

www.michelvandermeulen.com


What did you think about this post?