The Sprint Review is an event within the Scrum framework designed as a collaborative working session for a team to showcase finished work. It is an opportunity for the team and other relevant parties to discuss the product’s progress and direction. The meeting encourages open communication and hands-on examination of the work completed.
What Is a Sprint Review?
A Sprint Review is the second-to-last event of a Sprint, which is a fixed-length period of work. Its main purpose is to inspect the Sprint’s outcome and determine future adaptations. The focus of this session is the “Increment,” which is the sum of all Product Backlog items completed during the Sprint that creates a usable version of the product.
This event is a working session, not simply a demonstration. The dialogue between the team and stakeholders assesses progress towards the overall Product Goal. Based on feedback and inspection of the Increment, attendees collaborate on what to do next, which often leads to adjustments in the Product Backlog. The Sprint Review is timeboxed to a maximum of four hours for a one-month Sprint and is shorter for shorter Sprints.
Who Attends a Sprint Review?
The Sprint Review brings together the Scrum Team and key stakeholders. The Scrum Team consists of the Product Owner, the Scrum Master, and the Developers, with each member having a distinct function. The Product Owner explains which items from the Product Backlog have been completed and which have not.
The Developers lead the demonstration of the finished work, explaining what went well, any problems they encountered, and how those issues were resolved. They also answer questions about the Increment. The Scrum Master ensures the event takes place, that attendees understand its purpose, and facilitates the conversation as needed.
Key stakeholders are also active participants and can include customers, end-users, or company executives. Their role is to provide feedback on the product increment, ask questions, and contribute to the discussion about future work. This direct collaboration ensures the team is building a product that meets user needs and business objectives.
What Happens During a Sprint Review?
A Sprint Review follows a structured agenda to facilitate collaboration. The Product Owner starts the meeting by explaining the Sprint Goal and reviewing which Product Backlog items were completed. They may also discuss any items that were not finished.
Following this introduction, the Developers discuss the practical aspects of the Sprint, sharing insights into their process and any challenges they faced. This is followed by a live demonstration of the Increment where Developers showcase the new functionality. This is an interactive session where attendees can ask questions about how it works.
The entire group then collaborates on the path forward. This discussion is informed by the demonstration, feedback, and any shifts in the marketplace. The conversation also covers practical considerations for future releases, such as timelines and budgets. The outcome is a refined Product Backlog that reflects new insights, setting the stage for the next Sprint Planning session.
Sprint Review vs Sprint Retrospective
A common point of confusion is the difference between the Sprint Review and the Sprint Retrospective. Although both occur at the end of a Sprint, they have different purposes and participants. The Sprint Review is focused outward on the product being built. Its goal is to inspect the product Increment and gather feedback from stakeholders to adapt the Product Backlog.
In contrast, the Sprint Retrospective is focused inward on the team’s process. This event is for the Scrum Team to reflect on the past Sprint. Participants discuss what went well, what could be improved, and how they work together. The goal is to create a plan for implementing process improvements in the next Sprint.
The attendees for each event are also different. The Sprint Review includes the Scrum Team and external stakeholders. The Sprint Retrospective is a private meeting strictly for the Scrum Team, creating a safe space for open discussions about their internal dynamics and workflow.
How to Have a Successful Sprint Review
Conducting a successful Sprint Review requires careful preparation and fostering the right atmosphere. To keep the event productive and efficient, consider the following practices.
- Prepare the demonstration in advance to ensure the new functionality is stable and ready to be shown, avoiding technical glitches.
- Invite the right stakeholders who can offer meaningful insights from a business or user perspective.
- Set clear expectations at the beginning of the meeting, reminding everyone that it is an informal, collaborative working session.
- Foster an atmosphere of open collaboration by encouraging questions and ensuring the discussion remains focused and constructive.
- Respect the timebox to ensure the meeting covers all necessary points without losing the engagement of attendees.