 | Sprint Review |
Overview
The Sprint Review is a presentation at the conclusion of the sprint that demos and reviews all features produced during the sprint. It is a chance to demonstrate to the team and to any interested stakeholders what has been developed and to get feedback that might affect future directions the team & product might take.
Attendees
All members of the Dev Team, including the Scrum Master / Team Leader, as well as the Product Owner attend the Review. Other stakeholders may attend, and may be invited, especially if they have a particular interest / stake in the newly developed features.
Objective
The Sprint Review is a chance for the PO to confirm that all stories are done. It also allows stakeholders and others to try out the new increment and to give feedback, possibly before a release. A completed increment represents an iteration. Before starting the next iteration, the Review provides a chance for stakeholders to determine whether a change is warranted in the direction of the product.
Timing
The Sprint Review occurs just after the completion of a sprint. It is prescribed to last 4 hours for a 4-week sprint (1 hour per week of sprint).
The Process
The Product Owner runs the Sprint Review. After welcoming stakeholders (previously invited by the PO), the PO explains the goals of the sprint and what is to be demonstrated.
The Dev Team then takes over, demonstrating all functionalities developed and discussing what worked well and what worked poorly. The PO asks any needed questions and determines whether each item was completed according to its acceptance criteria.
After the product has been covered, the PO contextualizes the new increment into longer-term goals for the product. The PO starts by presenting upcoming items on the Product Backlog as an indication of what the immediate plans are for further development. The PO and stakeholders (can) discuss how/when to release the increment and any changes in the market that may alter the direction of future development.
Form this point, the PO has the feedback necessary to determine what elements on the Product Backlog are ready for further refinement, and the process is almost ready to start over … as soon as the Sprint Retrospective is complete.