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
Learning Path
Apply agile practices
Transform how you manage your work with agile practices, including kanban and scrum frameworks.
Learning Path
Configure agile boards for Jira projects
Learn how to create and configure agile Jira boards so you can plan, prioritize, and estimate upcoming work.
Jira Essentials with Agile Mindset
Suitable for beginners, this live instructor-led full-day course will set up your whole team to understand how to use Jira with an agile methodology.