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:
Results we expect to come out from a Sprint Review according to my experience and researches are the following:
In a perfect world, the Sprint Review should look like this:
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!
Deliver better and faster value to your customers with the Jira automation platform. Watch this Demo Den series below to learn how to use the new interface and set up automation rules to help your te...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events