Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

The anatomy of a Sprint Review


The Anatomy of a Sprint Review - Introduction

We like Sprint Review, we show things, working things and have collaborative discussions about what we show, but is this all about showing? Is this all about playing out with our iteration? Or is it more?


Let's recap the purpose of the Sprint Review:

Based on what was done during the Sprint, attendees collaborate on the next Product Backlog Items from the Product Backlog that could be done to optimise the value of the Product. The presentation increment (Sprint Review) is intended to elicit feedback and foster collaboration, hence the entire group collaborates on what to do next, so that the Sprint Review provides valuable input to subsequent Sprint Planning.


During the Sprint Review we might want some inputs from our Stakeholders, like sharing and giving information about:

  • How the marketplace or potential use of the product might have changed and what is now the most valuable thing to do next
  • The timeline, budget, potential capabilities and marketplace for the next anticipated releases of functionality and capability of the product
  • How the marketplace looks like (and after this, shall we change the Product Backlog?)
    • holidays, special events..
    • organizational periodical (new laws that come in and change your product, competitors updates ..)


Results we expect to come out from a Sprint Review according to my experience and researches are the following:

  • A revised Product Backlog that defines the probable Product Backlog Items for the next Sprint. Product Backlog may also be adjusted overall to meet new opportunities.
  • Reshape the "vision" for the product (during sprint iteration we get too much technical and we forget about the vision and the sprint goal)
  • Briefly, BRIEFLY, discuss the sprint itself (what went well, what problems we faced, show the increment), give stakeholder ability to try the increment with their hand (tablet, macbook..)
  • After the Product Owner shows the current state of the Product Backlog, we ask ourselves: shall we change something or continue like this?
  • The only one question to make constantly is: should we change the Product Backlog? Priorities?


In a perfect world, the Sprint Review should look like this:

  • "PO" owns the meeting, send invitation, put Product Backlog on the wall, open the session and tell Stakeholders the overall sprint burn down
  • "Development Team" briefly show the results (what actually is done)
  • "Stakeholders" try out physically the product and the passive lookers notes down observations


How much time should a Sprint Review last? At most two-hour meeting for two-week Sprints.


So what is the anatomy of your Sprint Reviews?

Hope this might have helped you to bring more clearance on Sprint Reviews and how you might get them to the next level in your organisation. Thank you for reading!


Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
May 07, 2019

I have worked in a few companies and many teams that have sprints but none of these have ever involved regular sprint reviews - they have always been on the nice-to-have-but-we-are-not-ready list of agile ceremonies.

Thanks for this article.

Like denis_mullaraj likes this

Hope you can benefit from the things I pointed out and possibly make Sprint Reviews a better opportunity to learn and adapt. Thank you for reading!

Like Kat likes this
We maintain the focus on the Sprint goal, achievements and shortly point out evolutives maintainance tasks.
Product Backlog was previously organized by the dev team, the PO validates the priorities and then the dev team estimates as much history point as needed for the next Sprint. PO validates and we start the new iteration.
Like denis_mullaraj likes this

Yep! Thanks for sharing your experience ;)


Log in or Sign up to comment
AUG Leaders

Atlassian Community Events