Sprint Review

Sprint Review Definition

A Sprint Review is a key event in the Scrum framework where the Scrum Team and stakeholders come together to inspect the Increment and adapt the Product Backlog. It is an opportunity to showcase the work completed during the Sprint and gather feedback from stakeholders to ensure the product is on track.

What is a Sprint Review?

A Sprint Review is a collaborative meeting that takes place at the end of each Sprint in Scrum. It serves as a platform for the Scrum Team to demonstrate the Increment they have developed and receive valuable feedback from stakeholders. The primary goal of the Sprint Review is to inspect the Increment and adapt the Product Backlog based on the feedback received.

During the Sprint Review, the Scrum Team showcases the work completed during the Sprint, highlighting the features and functionality that have been added to the product. The stakeholders, including customers, users, and other relevant parties, can attend the review and provide their input. This feedback is crucial for the Scrum Team to understand if they are meeting the expectations and requirements of the stakeholders.

Sprint Review Examples

1. Example 1: A software development team completed a two-week Sprint. During the Sprint Review, they demonstrate the new features they have implemented, such as a user registration module and search functionality. The stakeholders provide feedback on the usability and suggest improvements for the next Sprint.

2. Example 2: A marketing team has been working on a campaign for a new product launch. In the Sprint Review, they present the marketing materials they have created, including social media posts, email newsletters, and website banners. The stakeholders review the materials and provide feedback on the messaging and design.

Sprint Review vs. Retrospective

While the Sprint Review and Sprint Retrospective are essential events in Scrum, they serve different purposes. The Sprint Review focuses on inspecting the Increment and gathering feedback from stakeholders, while the Sprint Retrospective reflects the Sprint itself and the team’s processes.

What should be in a Sprint Review?

A Sprint Review should include the following elements:

1. Demonstration of the Increment: The Scrum Team showcases the work completed during the Sprint, highlighting the new features, bug fixes, or any other changes made to the product.

2. Feedback from stakeholders: The stakeholders provide input on the demonstrated Increment, sharing their thoughts, suggestions, and concerns. This feedback helps the Scrum Team understand if they meet the stakeholders’ expectations.

3. Adaptation of the Product Backlog: Based on the feedback received, the Scrum Team collaborates with the stakeholders to adapt the Product Backlog. This may involve reprioritizing user stories, adding new items, or changing existing ones.

What questions should I ask during a Sprint Review?

During a Sprint Review, it is important to ask relevant questions to gather feedback and ensure the product is aligned with the stakeholders’ needs. Some questions to consider asking are:

1. What do you think of the new features implemented in this Sprint?

2. Do you want to see any additional features or changes in the product?

3. How satisfied are you with the progress made during this Sprint?

4. Are there any usability issues or bugs that must be addressed?

5. Is the product meeting your expectations and requirements?

Wrap up

A Sprint Review is a crucial event in Scrum where the Scrum Team and stakeholders come together to inspect the Increment and adapt the Product Backlog. It provides an opportunity for the team to showcase their work, gather feedback, and ensure the product is on track to meet the stakeholders’ needs. By actively involving stakeholders in the review process, the Scrum Team can make informed decisions and continuously improve the product.”