Sprint Review - Learn Scrum

Scrum Framework Library - Sprint Review

What is the purpose of the Sprint Review meeting?

The purpose of the Sprint Review meeting is to inspect the Increment that was developed during the Sprint, gather feedback from stakeholders, and adapt the Product Backlog if necessary.

The Sprint Review meeting is a collaborative session held at the end of each Sprint in Scrum. Its purpose is to present the Increment developed during the Sprint to stakeholders and receive their feedback. The Sprint Review provides an opportunity to inspect the work done, demonstrate the product's functionality, and gather input that can influence future development. The meeting also serves as a platform for the Product Owner to refine the Product Backlog based on the feedback received.

The Sprint Review should be attended by the Scrum Team, stakeholders, and anyone else interested in the product's development.

The Sprint Review should be attended by the Scrum Team, including the Product Owner, Scrum Master, and Development Team. Additionally, stakeholders such as customers, end-users, management, and other relevant individuals should be invited to attend. The meeting is open to anyone interested in the product's development and can provide valuable feedback on the Increment. It is important to have a diverse representation of stakeholders to ensure a comprehensive perspective during the review.

The Increment is demonstrated during the Sprint Review through a live presentation or a walkthrough of the product's functionality. It is then evaluated based on the acceptance criteria and feedback from stakeholders.

During the Sprint Review, the Development Team demonstrates the Increment developed during the Sprint. This can be done through a live presentation, a walkthrough of the product's features, or any other suitable method. The team showcases the product's functionality, highlighting the user stories or features that were completed. Stakeholders evaluate the Increment based on the acceptance criteria defined for each item and provide feedback on its usability, quality, and alignment with their needs. The evaluation helps identify any necessary refinements or adjustments to be made.

Stakeholders can provide feedback and contribute to the refinement of the Product Backlog during the Sprint Review by sharing their observations, suggestions, and priorities.

Stakeholders can provide feedback and contribute to the refinement of the Product Backlog in several ways:
- Observations and suggestions: Stakeholders can share their observations and suggest improvements or enhancements based on their experience with the Increment.
- Prioritization: Stakeholders can express their priorities and preferences for certain features or user stories, which can influence the Product Owner's decisions when refining the Product Backlog.
- User feedback: Stakeholders, particularly end-users, can provide valuable insights into the usability, effectiveness, and satisfaction with the product, helping to shape future development efforts.
- Alignment with business goals: Stakeholders can provide feedback on how well the Increment aligns with the overall business goals, strategic objectives, and market demands.

The Sprint Review is a forum for stakeholders to actively participate, share their perspectives, and contribute to the refinement of the Product Backlog based on their feedback and insights.

Based on the outcomes of the Sprint Review, the Product Owner updates the Product Backlog, incorporating feedback and reprioritizing items as necessary. The team may also identify opportunities for process improvements.

The outcomes of the Sprint Review can lead to the following actions:
- Product Backlog refinement: The Product Owner incorporates feedback received during the Sprint Review into the Product Backlog. This may involve updating user stories, adding new items, or reprioritizing existing ones based on stakeholder input and changing requirements.
- Adjusting the Sprint Goal: If necessary, the Sprint Goal may be refined or redefined based on the feedback received during the Sprint Review.
- Process improvements: The team may identify opportunities for enhancing their development process or addressing any bottlenecks or challenges encountered during the Sprint. These insights can be used to improve future Sprints and overall team performance.

The actions taken after the Sprint Review help ensure that the product development efforts remain aligned with stakeholder needs and continue to deliver value to the end-users.