During each sprint, the development team creates potentially shippable product increments. The Sprint Review is an informal meeting where the team collaborates on what they achieved during the previous sprint and gets feedback on their product increments from key stakeholders. The feedback is then used to revise the product backlog. So, the meeting is all about inspect and adapt.
Purpose
A Sprint Review Meeting is an informal meeting which has the aim to collaborate about what was done in the previous sprint. It is not a status meeting but a demonstration of the product increments to get feedback and foster collaboration. The presentation of the product increments should be kept simple and transparent. Therefore, the use of PowerPoint slides is typically forbidden and preparation for the meeting should not take longer than two hours. One big advantage of a Sprint Review Meeting is that all relevant stakeholders are included in the project on a regular basis.
Attendees
Attendees include the Scrum Master, the development team, the Product Owner and key stakeholders which are invited by the Product Owner.
Meeting structure
The Scrum Master is responsible that the event takes place and every participant understand its purpose. The Product Owner determines in advance whether the requirements are satisfied or not and explains what product backlog items have been “Done” and what have not been “Done”. He discusses the product backlog as it stands and presents the goal of the sprint, which was determined during the previous Sprint Planning Meeting. The development team demonstrates the work which is “Done” to the stakeholders and answers questions about the increment (=potentially shippable product increment). It also informs stakeholders about key decisions which were made during the sprint. The team also gives feedback on what went well during the sprint and problems they ran into and how those problems were solved. All participants of the meeting get the chance to share their opinion on the product increments. Based on that the entire group collaborates on what can be done next to optimize the value of the product. The outcome of a Sprint Review Meeting is an evaluation and feedback of the product increments based on specific goals which were set in the previous Sprint Planning Meeting as well as a revised Product Backlog.
As all meetings in Scrum also the Review Meeting is time-boxed. The rules is usually the following:
· One week sprint = 1 hour Sprint Review
· Two week sprint = 2 hours Sprint Review
· Four week sprint = 4 hours Sprint Review
Common mistakes
· Turning the Sprint Review into a status meeting
The focus of the meeting should not be to demonstrate how much time the team needed, how much resources they spent, etc. The Sprint Review´s main focus is on results. It is about demonstrating how new functionalities are working, getting feedback from stakeholders and identifying room for improvement.
· Presenting “undone” backlog items
It is not valuable to present stakeholders what the team did during the sprint and which features are almost finished. Again, it is much more important to show them results in the form of finished backlog items. The focus of the meeting is to demonstrate the real value to stakeholders.
· The Product Owner sees the results for the first time
The Product Owner is part of the SCRUM team. Therefore his/her feedback is valuable during a sprint – not only at the sprint review. The product owner decides in advance about what product backlog items are done and only those are presented in the Sprint Review.
· Focusing on technical details
Again, the aim of the meeting is to get beneficial feedback from the stakeholders. For this objective it is not important to showcase every technical detail of the solution and demonstrate how it has been implemented. It is more important to focus on how the new feature/product etc. can be used and what benefits it has to the stakeholders.
Sources retrieved on 4th May 2018:
Comments