---

What Is A Sprint Review Meeting? This Might Surprise You!

The Sprint Review Meeting happens at the end of the Sprint. A Sprint Review lasts no more than four hours for a one-month Sprint and is usually shorter for a shorter Sprint. One to two hours may be a practical choice for a shorter Sprint. Depending on the type of software and available infrastructure, the Sprint Review Meetings take place in a meeting room, in a lab or in the room of the Scrum team. (See also Scrum Sprint Retrospective Meetings - Goals and Best Practices)

The goal of the Sprint Review Meeting is to review the shippable product increment built during the Sprint and bring transparency to the product development process.

The Scrum Team members do not need to prepare a Powerpoint or Keynote presentation to show in the Sprint Review Meetings. (See also Sprint Review Meeting: Goals and Protips)They should instead spend their energy on the successful completion and demonstration of the Sprint outcome, which we call the shippable product increment.

The Scrum team demonstrates its work results. The Scrum Team and stakeholders inspect the outcome together and discuss progress toward the Product Goal. This is a working session for adaptation, rather than a Product Owner approval gate.

The Sprint Review Meeting enables the Product Owner to inspect the current status of the product and adapt the Product Backlog and discuss what to do next. Therefore, Sprint Review Meetings are another way of formal and practical application of "inspect and adapt".

Participants of the Sprint Review Meeting are the Scrum Team, the Scrum Product Owner, the Scrum Master. Key stakeholders, such as end-users, clients, and business representatives, collaborate with the Scrum Team during the Sprint Review.

In Sprint Review Meetings, everyone is allowed to deliver their feedback about the demonstrated product increment.

In this way, the Scrum team has the opportunity to get unfiltered and direct input from stakeholders for whom they're building the software.