Skip main navigation

New offer! Get 30% off one whole year of Unlimited learning. Subscribe for just £249.99 £174.99. New subscribers only. T&Cs apply

Find out more

Sprint Reviews

A Sprint Review is held at the end of each Sprint and offers the team an opportunity to demonstrate to stakeholders what they accomplished during the

A Sprint Review is held at the end of each Sprint and offers the team an opportunity to demonstrate to stakeholders what they accomplished during the Sprint.

The next step in the process flow will be the Sprint Review.

components of all scrum activities illustrated in a process graphic starting with sprint planning, moving to the sprint backlog, then the daily scrum, then on to the sprint review, and eventually ending with a sprint retrospective (Take a closer look)

This informal event, which can take up to two hours, also allows stakeholders an opportunity to provide feedback to the team. The stakeholders’ focus is on potential uses of the product under development and how well the product aligns with current marketplace demand.

If the demonstration doesn’t meet the stakeholders’ expectations, the stakeholders can discuss changes they would like to see with the team. It is very satisfying for the Development Team to demonstrate all work completed that meets the Definition of Done. Based on conversations between the Product Owner, Stakeholders, and Scrum Team, new Product Backlog items may be added for later prioritization and discussion.

Attendees in a Sprint Review meeting usually include:

  • Scrum Master: Ensures the event takes place and communicates the event’s time frame and purpose
  • Development Team (Primary Members): Conducts the demonstration and gathers stakeholder feedback
  • Product Owner: Gathers feedback and answers questions that may arise
  • Stakeholders: Participate at the invitation of the Product Owner and may include some members of management, customers, and possibly even developers from other projects.

The Sprint Review runs as follows:

  1. The Product Owner starts with an explanation of Product Backlog items in the ‘Done’ state along with items not yet ‘Done’.
  2. Development Team members describe things that went well, challenges that came their way, and how those issues were resolved.
  3. Development Team members give a demonstration of all work that is ‘Done’ and respond to attendees’ questions.
  4. The Product Owner discusses remaining Product Backlog items providing anticipated target and delivery dates.
  5. The group as a whole collaborates on identifying the next steps that will be part of the input for upcoming planning—including possible marketplace changes that may need to be incorporated.

The Sprint Review is an insightful event resulting in a revised Product Backlog that may include adjustments needed to address new marketplace opportunities. It is used as a team-building event where trust is strengthened across the Scrum team.

Watch this

The following video gives an overview of the Sprint Review meeting, the role players, and the activities that are involved.
Watch the Sprint Review meeting here.

You can now see how Daily Scrum and Reviews work hand in hand. The final Scrum activity that we will take a look at is the Retrospective.

This article is from the free online

Advanced Agile with Scrum and Kanban

Created by
FutureLearn - Learning For Life

Reach your personal and professional goals

Unlock access to hundreds of expert online courses and degrees from top universities and educators to gain accredited qualifications and professional CV-building certificates.

Join over 18 million learners to launch, switch or build upon your career, all at your own pace, across a wide range of topic areas.

Start Learning now