How can you keep sprint reviews focused on feedback and learning?

1 Set clear goals and agenda

Before the sprint review, you should define the goals and agenda of the session and communicate them to the participants. The goals should align with the sprint goal and the product vision, and the agenda should cover the main features or user stories to be demonstrated, the feedback questions to be asked, and the time allocation for each topic. Having clear goals and agenda will help you keep the sprint review on track and avoid irrelevant or redundant discussions.

2 Prepare a demo and a feedback format

The demo is the core of the sprint review, where you show the working product increment and its value to the users. To prepare a good demo, you should select the most relevant and impactful features or user stories, test them thoroughly, and rehearse them beforehand. You should also choose a feedback format that suits your needs and preferences, such as surveys, polls, ratings, or open-ended questions. The feedback format should be easy to use, capture the key aspects of the product, and encourage honest and constructive responses.

3 Invite the right people and engage them

The sprint review is not only for the team and the product owner, but also for other stakeholders who have an interest or influence on the product, such as customers, users, managers, or sponsors. You should invite the right people who can provide valuable feedback and insights, and inform them about the goals, agenda, and expectations of the sprint review. You should also engage them during the session, by asking them questions, listening to their opinions, acknowledging their contributions, and thanking them for their time.

4 Handle feedback with openness and respect

Receiving feedback in the sprint review is an invaluable opportunity for learning and improving your product and process. However, it is important to keep an open mind and handle feedback with respect. Avoid taking feedback personally or defensively, arguing or justifying decisions, ignoring or dismissing feedback, or promising or committing to anything. Feedback should be seen as a chance to learn and understand different perspectives, as well as a gift to help improve your product and customer satisfaction. Evaluate feedback carefully and prioritize it accordingly.

5 Review and act on feedback

The sprint review is not done when the session ends; it's important to review and act on the feedback collected. Summarize and document the feedback by organizing it into themes, categories, or action items and recording it in a transparent format. Analyze and prioritize the feedback according to relevance, importance, urgency, and feasibility, as well as your product vision, strategy, and roadmap. Finally, plan and implement the feedback by incorporating it into your product backlog, refining it into user stories or tasks, and assigning it to future sprints. By following these steps, you can ensure that sprint reviews are focused on feedback and learning, making them more effective and enjoyable for everyone involved.

6 Here’s what else to consider

This is a space to share examples, stories, or insights that don’t fit into any of the previous sections. What else would you like to add?