Sprint Review: Getting Real Stakeholder Feedback
The Sprint Review is more than a demo. It is a critical event for inspecting the Increment and adapting the Product Backlog. Learn how to get actionable feedback.
The Sprint Review is a working session, not a presentation. It is the second to last event of the Sprint. Its purpose is to inspect the Increment and adapt the Product Backlog if needed. The Scrum Team presents the results of their work to key stakeholders and collaborates on what to do next. This is where real feedback happens, or it should. Without good feedback, the Scrum Team risks building the wrong thing.
Invite the Right People
Who attends the Sprint Review matters. The Scrum Team must be there. Key stakeholders are also essential. These are people whose input is valuable for the product. They might be users, department heads, or other internal teams. The Product Owner decides who to invite. If the right people are not there, the feedback will be limited. You need people who can provide context, challenge assumptions, and make decisions about future direction. Without them, the Review becomes a show and tell, not an inspection and adaptation.
Demonstrate the Working Increment
The core of the Sprint Review is the demonstration of the Increment. This is not a slide deck. It is the actual working product. The Developers show what they built and how it functions. This makes the work transparent. Stakeholders see and interact with the product. This interaction is crucial for generating useful feedback. For example, if a team builds a new search filter, they should show it working with real data. They should let stakeholders try it. Watching a demo on a screen is one thing. Clicking buttons and seeing results is another. This direct experience helps stakeholders identify usability issues, missing features, or misunderstandings quickly.
Focus on Collaboration and Conversation
After the demonstration, the Scrum Team and stakeholders discuss what was done. They talk about the progress toward the Product Goal. They review the Product Backlog as it stands. This is a conversation. It is not a one way street where the team presents and stakeholders listen. The Product Owner facilitates this discussion. They gather input on potential new items, changes to existing items, or adjustments to the product vision. This collaborative discussion informs the next steps.
An example of good collaboration: A team demonstrates a new reporting module. A sales manager says, 'This looks good, but can we also filter by region?' Another stakeholder, from marketing, adds, 'And can we export it to CSV?' This direct input immediately informs the Product Backlog. The Product Owner can then work with the team to prioritize these new insights.
What Good Feedback Looks Like
Good feedback is actionable. It is specific. It helps the Product Owner refine the Product Backlog. It is not vague praise or criticism. It focuses on the Increment and its value. Here are characteristics of effective feedback:
- Specific: 'The navigation for this new feature is not intuitive' instead of 'I do not like it'.
- Actionable: 'Could we add a 'save as draft' option here?' instead of 'It needs more functionality'.
- Value-oriented: 'This will save our support team three hours a week' instead of 'It is a nice feature'.
- Timely: Given during the Review, not days later.
- Constructive: Focused on improvement, not blame.
The Scrum Team must create an environment where stakeholders feel comfortable providing this kind of feedback. This means listening actively and asking clarifying questions. It means thanking them for their input, even if it highlights problems.
Adapting the Product Backlog
The ultimate outcome of the Sprint Review is an updated Product Backlog. Based on the feedback and discussion, the Product Owner adjusts the Product Backlog. This might mean adding new items, reordering existing items, or removing items that no longer seem valuable. The entire Scrum Team and stakeholders collaborate on this. The Product Backlog is a living artifact. It reflects the latest understanding of what is most valuable to build next. The Sprint Review ensures this understanding is shared and updated regularly. This continuous adaptation is how Scrum ensures the team is always working on the most important things.