The Sprint Review meeting is a time-limited event in Scrum. The maximum duration is four hours for a four week Sprint and proportionally less for smaller Sprints. The Sprint Review takes place at the end of the Sprint or iteration and is used to demonstrate the work that was done during the Sprint.
The Sprint Review is conducted by any member of the team. People who may be present include the Scrum Team and any other external customers, stakeholders, or interested persons that the Product Owner may invite. The Sprint Review generally consists of a demonstration of the work done. However, ‘demonstration’ is not the sole or main objective of the review.
The atmosphere of a Sprint Review is collaborative. The Product Owner identifies which features have been completed. The team reviews how much work it was able to handle, whether the backlog was removed from Sprint, and what remains. The team analyzes the backlog items and they are returned to the product backlog for reprioritization. The team answers any questions about the work done.
This is an important time for team members to interact with the Product Owner and understand what is happening with the product. Part of the Sprint Review can also be used to reorder the Product Backlog and discuss current business priorities with the Product Owner. Items from the Product Backlog are discussed and the team considers what it might address in the next Sprint. This sets the stage for the next planning meeting.
unique appearance
The work done in the Sprint is shown as a group effort. Commendations or commendations are given to the entire team and not to an individual. Likewise, this is not used as an opportunity to point fingers in case there are any pending items left. The team takes collective responsibility for the outcome of the Sprint and the lessons learned are for everyone.
The Sprint Review provides a valuable opportunity for the team to get organized and reach their potential. If the team could easily meet the Sprint backlog with the time remaining at the end of the Sprint, they realize it may take a few more hours in the next Sprint. If the team can’t finish the backlog items, consider taking fewer items next time or adding more buffer for contingencies.
It’s done’?
An important role that the Scrum Master plays is to ensure that the team and the Product Owner understand the success criteria for each item in the Product Backlog. Any item that does not adhere to the definition of ‘done’ decided above is not included in the Sprint Review. This item needs to be returned to the backlog to be prioritized again. A typical example would be an article that is coded but not tested or an article with open defects.
inspect and adapt
While the Daily Meeting is used to review a day’s work, the Sprint Review is an important time to “review” the steps taken throughout the Sprint period. The team adjusts its workload and ‘adapts’ its speed. After experimenting for a few iterations, the team gets a good idea of its speed and can then be more precise in its planning.
The team spends no more than thirty minutes preparing for the Sprint Review. The Scrum Master facilitates, as needed, ensuring that the Sprint Review meeting is completed in the allotted time.