The Sprint Review

The sprint review takes place at the end of each sprint. It is designed to be a meeting in which the team demonstrates the functionality of the product produced during the cycle so that the Product Owner can inspect it and decide whether or not it is fit for purpose. It is a very informal meeting, and it should be seen as a natural end result of the work carried out during the sprint.

Sprint Review Participants

Everyone involved and interested in the increment of software that has been produced should attend the sprint review. This includes all members of the Scrum team, especially the Product Owner, and the Scrum Master, as well as all key stakeholders such as customers and managers. In some cases, it may also make sense for developers from other projects to attend, particularly if they are working on features that interface or integrate with the software that has been built.

Purpose of the Sprint Review

Each sprint should produce a potentially shippable product increment. In other words, at the end of the sprint, the features produced should have been not only developed but also tested and be fully usable. During the session, all attendees are encouraged to collaborate and give feedback on what has and hasn’t been delivered. The members of the Scrum team also answer any questions raised by the other stakeholders on the deliverables. The Product Owner’s role in this meeting is crucial, as it is their responsibility to ensure that the features meet all of the acceptance criteria and can be marked as done. It is the Product Owner who must make a final decision on whether to accept or reject each piece of functionality as being fully complete according to the specifications. Any stories that should have been delivered but were not completed are re-estimated and will be scheduled for delivery in an upcoming sprint.

Recommended Further Reading

The following materials may assist you in order to get the most out of this course: