Sprint Review: Getting Real Stakeholder Feedback

The Sprint Review is a working session, not a formal presentation. Its purpose is to inspect the Increment and adapt the Product Backlog. This means getting real, actionable feedback from key stakeholders. Without their input, the Scrum Team risks building the wrong thing. A good Sprint Review fosters collaboration and transparency, aligning everyone on the path forward. It is the best opportunity to ensure the product development stays on track with market needs and user expectations.

Who Needs to Attend

The Scrum Team must attend. This includes the Product Owner, Scrum Master, and Developers. Beyond the team, the Product Owner is responsible for inviting relevant stakeholders. These are individuals who have a vested interest in the product and its success. They might be end users, customers, business unit leaders, or even compliance officers. The goal is to gather diverse perspectives. Limiting attendance to just a few internal managers defeats the purpose. The more varied the input, the better the decisions will be.

Focus on the Increment, Not Just a Demo

Many teams treat the Sprint Review as a demo. While demonstrating the Increment is part of it, the focus is broader. The Increment is the sum of all Product Backlog items completed during the Sprint and all prior Sprints. It must be usable. The Scrum Team presents what they have built. Then, they lead a discussion about it. This discussion is crucial. It is not about showcasing perfection. It is about presenting a working product and asking for constructive criticism.

The Product Owner also discusses the state of the Product Backlog. They outline what is likely to come next. This allows stakeholders to influence future work based on the new Increment and market changes. It is a forward-looking event as much as it is a backward-looking one.

Facilitating Effective Feedback

Getting useful feedback requires preparation and good facilitation. The Scrum Master often helps here. The Product Owner should guide the conversation to specific areas. Do not just ask, 'What do you think'. Ask targeted questions. For example, 'Does this new search filter help you find what you need faster' or 'What are your concerns about this new reporting feature'?

Consider these points for better feedback:

• Set clear expectations for stakeholders before the review. Explain its purpose.
• Provide a brief context for the Increment. What problem does it solve?
• Allow stakeholders to interact with the Increment directly if possible.
• Use open-ended questions to encourage detailed responses.
• Actively listen and take notes on all feedback, positive and negative.
• Avoid defensiveness. Feedback is about the product, not personal attacks.
• Summarize key takeaways and proposed next steps at the end.

Adapting the Product Backlog

The Sprint Review is an inspect and adapt event. The primary adaptation is to the Product Backlog. Based on the feedback and market conditions, the Product Owner will adjust the Product Backlog. This might mean reordering items, adding new ones, removing old ones, or refining existing ones. The Sprint Review helps the Product Owner make informed decisions about what to build next to optimize value. It is not a commitment to implement every piece of feedback immediately, but an input for the Product Owner's ongoing prioritization.

The Value of Continuous Feedback

A well-executed Sprint Review creates a continuous feedback loop. Instead of waiting months for user acceptance testing or a big launch, teams get feedback every Sprint. This reduces risk and waste. It ensures the team is always building the most valuable product. Regular, direct engagement with stakeholders builds trust and shared understanding. It makes product development a collaborative journey, not a series of handoffs. Embrace the Sprint Review as your most powerful tool for product direction.

Start with the Foundations module →

Or take the full Scrum Master track →