The Sprint Review for Scrum Masters

The Sprint Review meeting comes at the end of the sprint and the goal of this meeting is to have key people in the room to be able to assess the state of the product and align the backlog based on what the team shows. This is not just a presentation or demo, but rather a working session facilitated by the Scrum Master where key stakeholders can see the current state of the product and provide feedback on the deliverables. This meeting of stakeholders, end users, team members, product owner, and Scrum Master is an important closing step to a sprint cycle.

The Sprint Review

The purpose of the Sprint Review is to review the state of the deliverables from the current sprint. With the Scrum Master facilitating, this is a working session where feedback is welcome and encouraged to make sure the product is meeting the product vision. By having the stakeholders at the meeting, it allows for fast feedback and aids in creating a quick iteration cycle. This is also a great meeting for the stakeholders, end users, product owner, and team members to get to know each other and understand each other’s longer-term requirements.

Setting Expectations

The Product Owner or Scrum Master will set expectations for what will and will not be seen at the meeting. What was the focus of this sprint? Do some features still need a further effort? What will stakeholders see demonstrated at this meeting? What hasn’t completed this sprint and what were the roadblocks? This helps to frame everyone’s perspective concerning how complete a feature will be and will hopefully change attendees’ view on what level of feedback to give.

59 Seconds Agile - Sprint Review Meeting

59 Seconds Agile – Sprint Review Meeting


After setting expectations, it’s time for the demo to kick off. This is not a formal presentation but rather an informal meeting where anyone in the room can ask questions or provide feedback. It’s helpful to have the Scrum Master own the coordination of the demonstration while the Product Owner provides context for sprint decisions and features as they present each completed item. Some teams like having the people who worked on that feature present it to the group, other teams will opt to have the Scrum Master facilitate the entire meeting, with the team there to provide additional details. They will show off each item that was completed that sprint and let the room respond to it.

Guiding the Conversation

While this meeting might seem straightforward, it’s very difficult to make sure the room has the right tone and productive feedback is given to the team. This is where the Scrum Master steps in and helps to manage the conversation. The Scrum Master will ask to follow up questions when stakeholders give opinions to make sure the entire room is on the same page. They will also help steer the conversation should it start to go down a tangent that is not necessary for the entire room to be there to discuss. The Scrum Master is there to make sure everyone feels like their feedback is welcome but also making sure it’s given the appropriate context so team member’s don’t feel overwhelmed.

Wrapping Up The Sprint Meeting

To wrap up the Sprint Review, the Scrum Master or Product Owner will then speak about what will happen in the next sprint. Including, what will be shown in the next sprint review. This is also a great time to clarify any questions about the next sprint with end users. By getting this feedback every sprint it gives end users and stakeholders an opportunity to express any changes they might have for the backlog prioritization.

Prev <— Continue Reading —> Next

Our Favourite Agile Books

Read Our Reviews

The History of Agile For Scrum Masters

Prior to the 1990’s software development was very slow, often taking years to complete development and release the product to market. The industry was following a very formal methodology for products and software development…

Read More

What is Agile to the Scrum Master?

While traditional project management is still widely used, the benefits of an Agile approach to running a project are becoming more and more recognized. Where Agile has a distinct advantage over classic project management is the development of new products…

Read More

Why Use Agile as a Scrum Master?

When determining if a move to Agile is right, a PESTLE can be used to simplify what factors should be considered. While Agile is sometimes thought of as a software development project management method, it isn’t just for these types of technology-centric companies…

Read More

The Agile Manifesto For Scrum Masters

Agile is a quick, simple, lightweight and effective way of managing projects. In traditional project management models…

Read More

The Agile Principles For Scrum Masters

When the Agile Manifesto was drawn up in 2001, it embodied four values and twelve principles that signaled a new approach to…

Read More

The Agile Fundamentals For Scrum Masters

Thinking of becoming a Scrum Master? Or are you already one, but you’re still new to the job? No matter what level of experience…

Read More

The Declaration of Interdependence For Scrum Masters

The Declaration of Interdependence establishes that all members, stakeholders, and customers are interdependent and…

Read More

The Agile Frameworks For Scrum Masters

There are many different Agile frameworks – all of them share the same philosophy and are built around the Agile Manifesto and Principles. But they vastly differ in their approaches, values, and structure. …

Read More

The Scrum Framework For Scrum Masters

The Agile Scrum framework is designed to deliver products and projects of any size. This includes projects, programs, and portfolios. Scrum provides guidelines on delivery techniques, events, and roles. Many of the same ceremonies are held within both a standard Agile scrum project and an Agile Scrum…

Read More

The Scrum Roles For Scrum Masters

Scrum is a useful tool for the creation, maintenance, plan, and execution of diverse products and services. The tool consists of…

Read More

The Scrum Team Size For Scrum Masters

The basics of Scrum can be easy but implementing them and succeeding with Scrum can be infinitely harder. Scrum …

Read More

The Agile Project Vision For Scrum Masters

At the heart of any great product is a great vision. It describes the primary goal or goals of a product and creates a focus that…

Read More

Forming the Scrum Team For Scrum Masters

Scrum is a framework that encourages delivery of potentially shippable product increments every 2-6 weeks. The work is…

Read More

Developing Epics For Scrum Masters

The term ‘epic’ in agile refers to a large user story that has not yet been defined in detail. Typically, an epic will cover a single…

Read More

The Agile Product Backlog For Scrum Masters

A Product Backlog is an organized collection of the existing User Stories (aka Wants and Needs) for an explicit business endeavor. Think of a shopping catalog of User Stories, ordered by urgency, that can be perused and selected from to determine what will be worked on during the current…

Read More

Release Planning For Scrum Masters

Although flexibility and adaptability are part and parcel of an agile methodology, this does not mean that no planning is required when…

Read More

Creating User Stories For Scrum Masters

User Stories are an integral part of the agile development process. They are an important agile technique that is used to frame…

Read More

Estimating User Stories For Scrum Masters

One of the principles of self-managing teams in Agile Scrum is working collaboratively with the Product Owner to effectively deliver…

Read More

Creating Tasks For Scrum Masters

According to The Agile Manifesto: “The best architectures, requirements, and designs emerge from self-organizing teams.” As a…

Read More

Estimating Agile Tasks For Scrum Masters

In Scrum, a list of user stories is produced and put together to form a product backlog, and each of these user stories will need to…

Read More

Creating the Sprint Backlog For Scrum Masters

The Sprint Backlog is defined as a group of user stories that are grouped together during the Sprint Planning Meeting.  This…

Read More

Creating the Deliverables For Scrum Masters

Agile Scrum provides the framework for delivery of the vision of an organization. Execution of the vision includes processes, ceremonies and project deliverables that are also known as artifacts…

Read More

The Daily Stand-Up For Scrum Masters

The daily scrum is an opportunity for developers or anyone committed to working in the sprint to talk to each other to make sure the…

Read More

Product Backlog Prioritisation For Scrum Masters

The product backlog is a key element of Agile software development. It facilitates a development environment that creates valuable features and products for stakeholders…

Read More

The Sprint Review Meeting For Scrum Masters

The Sprint Review meeting comes at the end of the sprint and the goal of this meeting is to have key people in the room to be able …

Read More

Demonstrating and Validating the Sprint For Scrum Masters

As organizations migrate to Agile principles, there may be questions about how the organization can prove that there is value…

Read More

The Sprint Retrospective For Scrum Masters

A very simple step by step guide to help you choose the appropriate product development methodology from…

Read More

Releasing the Product For Scrum Masters

One of the most important milestones any project will ever have is finally releasing their product and putting it out there. It’s the…

Read More

Regression Testing For Scrum Masters

In companies using agile development, it is common to introduce changes in a product incrementally. Along with the new changes, unexpected issues may arise, testing whether the existing functionality is broken or not becomes very important…

Read More

Product Owners

Find out more about the Agile and the Product Owner Role

Read More


Find out more about the Agile and the Developer Role

Read More

More Articles

Read More

Chicken Appreciation Society

Translate »