When designing a flow for an event, it is hugely important to be clear on the purpose. For the Sprint Review , the purpose is to inspect the increment that was created during the Sprint as well as to adapt the Product Backlog based on new insights, ideas, and changes that result from this inspection. The Sprint Review is about answering the question: “Based on what we learned this Sprint, what are the next steps?”. This provides valuable input for Sprint Planning.
This recipe is an example and starting point with a number of different facilitation examples provided. Please inherit from it and make it your own. If you have a great idea please submit a new recipe
This workshop leverages a simple flow and consists of the following:
The Product Owner presents the vision and goals, followed by a summary of what happened, and a review of the product increment. Update the product backlog and discuss likely release dates and budgeting.
Although Scrum Masters can certainly facilitate the Sprint Review, there is nothing holding others back from facilitating. Since the Sprint Review is particularly important for the Product Owner, as he or she will be sharing the increment with stakeholders, it makes sense for him or her to also play a role.
The purpose here is for the Product Owner to set the tone and direction. Let’s be 100% clear to stakeholders, ourselves, and the customer that they are in control of what we build and if they get value or not.
There will always be Backlog Items that we were unable to complete during a Sprint. This is OK and just needs to be presented as here are the things that we did, and here are the things we did not get to. Did we meet the Sprint Goal?
Review both the Cycle Time Scatter Plot and the Throughput Run Chart to understand what happened during this Sprint.
Depending on the scale there are many ways to facilitate this. The more engaging the better. If you have a lot of stakeholder participation then more advanced techniques involving liberating structures encourage the most engagement.
The main purpose of the Sprint Review is actionable feedback and updating the Product Backlog to reflect what’s next, based on what just happened. Guide the feedback and facilitate the engagement of stakeholders. It is never good enough to just ask for feedback!
Share what is the rough draft plan for the next Sprint. Share your teams Service Level Expectation (SLE) and what the options are for Sprint Goals.
You can use a Throughput Run Chart to present predictions based on empirical data with your expected confidence levels._
Based on our historical data and our Service Level Expectation (SLE) you should be able to answer any Stakeholder questions on “When will I get feature A?” or “When will Feature B ship?”. Express all your predictions coupled with your confidence level of achieving it.
Use a Monte Carlo How Many or Monte Carlo Whenn to answer Stakeholder questions like “What will I get by 23/01/2024?” and “When will item x be completed?” As this is calculated using your team’s historical data you will need to discuss the Service Level Expectation for the Team(s).
Do you have architectural reviews, technology overviews or legal compliance? Discuss them here.
Just as it says!
If you've made it this far, it's worth connecting with our principal consultant and coach, Martin Hinshelwood, for a 30-minute 'ask me anything' call.
We partner with businesses across diverse industries, including finance, insurance, healthcare, pharmaceuticals, technology, engineering, transportation, hospitality, entertainment, legal, government, and military sectors.
CR2
NIT A/S
