Sprint Review: It’s Not Just A Demo

Reading Time: 3 minutes

What is a sprint review?

It’s a meeting for the Team to get together for a demo, or show-and-tell, at the end of a Sprint that what they done.

The Scrum framework calls for the completion of product promotions that can be submitted during each run. Therefore, you should be able to show a fully functional feature, or set of features, at the end of each Sprint. Therefore, think of this meeting as a celebration of its accomplishments.

Scrum sprint review meetings are held throughout the sprint before the retreat meeting marking the end of the sprint.

Sprint Review or a Demo?

Many of those who do Scrum by mistake call Sprint Review Demo. Is it just a matter of terminology? In my opinion, the Sprint Review Scrum event is highly underestimated, and for many companies, its potential is yet to be revealed. It is true that the Exhibition or Short is an important part of the Sprint review, but it is not the only one.

What is the purpose of the sprint review?

The main purpose of this meeting is to answer a simple question:

Did the Team Achieve the Goal that set at start of sprint?

To be clear, even if the answer is a resounding no, Sprint Review should see the team for completed work. Everyone should actively participate in the Sprint review by providing questions, comments, or concerns (well!) On the work done.

Other benefits of sprint review meetings include:

  • Improving the quality of end products
  • Keeping participants involved by asking for and using their feedback
  • Helping your team maintain good teamwork habits
  • Disclosure of the project
  • Review sprint backlog and prioritize (if necessary) story points
  • Motivate your team and show appreciation

This review session helps to shape future athletes. For example, based on what the engineers are showing, the team may need to make changes to the product backlog before the next run. Whether this is possible is based on the following conditions:

Whether the team met the original targets set during the Sprint planning meeting

What information is provided by those present during the Sprint review

If your Sprint review is starting to feel outdated one reason is that you may have focused on showing off the finished work. Do not forget to make these meetings participatory so that each team member can give their opinion on the completed work. This is a great opportunity for open discussion.

Who attends the Sprint Review:

Scrum team and stakeholders (users, other teams, managers, investors, sponsors, customers, etc.) One can say that we invite the whole world to review the Sprint and this is absolutely true

How the Sprint Review Is Conducted:

The Product Owner opens the meeting and tells attendees what the Development Team is doing during the current Sprint (what is “Done” and “not done”).

The Development Team demonstrates the “Done” (Demo) activity, answers questions and discusses problems they encountered along the way.

The Product Owner discusses the current Background Product status, market changes, and predicts release dates.

Attendees of the event collaborate on Product Backgrounds, which can be completed during the next Sprint. Thus, participants gain a shared understanding of future work.

A review of the budget, timeline, potential skills follows.

Opportunity To Inspect And Adapt

Sprint is one of the five official Scrum Events and is an opportunity for the Scrum Group to practice strength. Here is a brief summary of what we are testing and changing during the Sprint review.

Inspect : Sprint, Product Backlog, Enlargement, Market Place, Budget, Time Line, Skills.

Adapt: Product backlog, Release Program.

Good Sprint Review Practices

  • An informal gathering with coffee and cookies that looks like a meeting, often held as an Expo or Review Bazaar.
  • Product backlog is updated after / during the Sprint update.
  • The meeting is usually attended by end users.
  • The Development Team communicates directly with end users and stakeholders and receives direct feedback from them.
  • The “Done” product is displayed in workplaces where participants can play with new functionality.

Signs of An Unhealthy Sprint Review

  • Official / status meeting.
  • New activity is only shown in slideshow.
  • The Product Owner “accepts” the work completed by the Development Team.
  • The Development Team does not exist (fully) yet.
  • They are not participants and / or end users.
  • Performance shown does not meet the definition of “Done”.
  • Product History not updated. The Scrum team operates in the previously defined scope.
  • Participants “receive” the completed work from the Product Owner.


The Sprint update is more than just a Demo. Sprint Review is a place to discuss market changes, review the completed Sprint as an event, review the release plan, discuss product backlogs and possible focus on the next Sprint. This is where the discussion between Scrum Team and stakeholders took place and feedback on product promotion. A number of changes in Product Backlog can be an important indicator of how healthy your Scrum is.

Visit Knolway to access more resources.