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!
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!
Recommended Learning For You
Level up your skills with Atlassian learning
Visualizing Work Across Teams with Plans in Jira Software
Learn how to use Plans to accurately map your team’s work and make better recommendations.
The Beginner's Guide to Agile in Jira
This course has everything you need to get started with agile and Jira Software.
Atlassian Certified Associate
Jira Software Board Configuration
Earn an associate-level credential from Atlassian that shows you can effectively configure Jira Software boards.