Use this template to showcase your product increment items and gain insightful feedback from the key stakeholders.
Mark what you have accomplished in this sprint session and write down any feedback from the attendees.
The development team demonstrates the product increment to the product owner.
The product owner examines whether the demo fits the product backlog agreed upon during the sprint planning meeting.
Any interested party can comment on / provide feedback based on the product demo.
Write down any highlights that inspired you...
set action items
The sprint review meetings occur at the end of each sprint, followed by a sprint retrospective meeting. It is complementary to the sprint planning meeting, where the team decides which product backlog items to accomplish in this sprint. In the sprint planning meeting, the development team and the product owner choose a set of product features to add or improve, while the sprint review meeting is a reporting and evaluative process.
Unlike other scrum meetings, key stakeholders, such as the end users, are welcome to join the sprint review meeting so that the development team and the product manager can gain straightforward insights into a better product.
The sprint meeting is not just a demo. While the product increment demonstration by the development team is a crucial part of the meeting, the more important thing is for stakeholders (e.g., the end users) to understand and provide valuable feedback to the team so that the product can reach its maximum value potential.
Sprint review and the sprint retrospective are not interchangeable in practice. The two types of meetings are equally important for the success of a sprint session and the integrity of the Scrum framework. Essentially, sprint review focuses on maximizing the product value, while sprint retrospective revolves around making continual process improvements.