Sprint Review: measuring value and gathering feedback

The Sprint Review marks the moment when the team looks back at the results delivered in the past Sprint and gathers direct feedback from stakeholders. At Spark Academy, we see that a well-organized Sprint Review helps validate whether the team is still on the right track and simultaneously provides inspiration for improvements or new ideas. By collecting feedback at this stage, you prevent discovering too late that you might be heading in the wrong direction.

‍

What is the Sprint Review and how does it work?

The Sprint Review is an open meeting where the entire Scrum Team and relevant stakeholders come together. The goal is to assess what has been delivered in the past Sprint and to jointly discuss whether your product still aligns with current needs and priorities. During this session, the team can give a demo of the delivered Increment, ask for feedback, and collectively decide what adjustments are needed for the future.

Typically, the Sprint Review begins with a brief explanation from the Product Owner about the goals set for that Sprint. Afterwards, the Development Team demonstrates what has actually been achieved. Stakeholders can ask questions, provide feedback, and make suggestions. Based on this input, the Product Owner can decide to adjust the Product Backlog. This creates a continuous process of inspection and adaptation, ensuring that the product moves a step closer to the desired outcome each time.

‍

Who is responsible?

• Product Owner: Invites stakeholders and shares the Sprint Goals established at the beginning of the Sprint. The PO also gathers feedback to update the Product Backlog.
• Development Team: Demonstrates the delivered work and is open to questions and suggestions.
• Scrum Master: Facilitates the Review, manages time, and ensures everyone understands the session's purpose.

‍

The Role of the Scrum Master

As a Scrum Master, you ensure that the Sprint Review doesn't devolve into a formal presentation. It is pre-eminently a moment to jointly discuss what went well, what could be improved, and what new ideas have emerged. This means:

• Assisting with preparation, for example, by advising the team on how to demonstrate the Increment.
• Ensuring that stakeholders feel heard and that their feedback is recorded.
• Encouraging a constructive discussion that covers both successes and challenges.
• Collaborating on the next steps and changes that can be incorporated into the next Sprint or the Product Backlog.

‍

Common Pitfalls

• Too Superficial Feedback: If stakeholders don't actively participate or are hesitant to make critical remarks, the Review remains too vague.
• No New Insights: Sometimes the Review becomes a ritual where only what has been built is shown, without discussion about the direction or the bigger picture.
• Lack of Follow-up: When feedback is not directly incorporated into the Product Backlog, the added value of the Review is largely lost.

‍

The Sprint Review gives teams and stakeholders the opportunity to collaboratively adjust course and maintain focus on the right goals. By showcasing what has been built at this point, you not only get the chance to validate your product but also to gather new ideas, suggestions, and plans. The Scrum Master plays an important role here as a facilitator and a catalyst for open communication. Thus, the Sprint Review becomes not just a control mechanism, but primarily a valuable moment for learning and continuously improving the product.

‍