The movie sprint retrospective
This format can be used for a sprint retrospective, in the theme of movies. The structure behind this format is the same as “what went well”, “what didn’t go too well”, and “what can we do try or do differently next time”. If you have movie enthusiasts in your team, this can be a fun format to try.
As an icebreaker, as every participant to put an Oscar on the picture that best represents their experience of the sprint. You can also ask everybody to share a few words why they chose this picture. Prevent going into detailed discussions at this point, as this is part of the next step in the retrospective.
The retrospective format
This retrospective consists of 3 stages:
- “Barbie (Fantastic):” what was fantastic last sprint? What went really well and/or deserves kudos?
- “Oppenheimer (Dramatic):” what was dramatic last sprint? What went really bad or was difficult?
- “Spiderman (Different):” looking in hindsight, what could we have done differently that would have made the last sprint easier for us?
After explaining the stages to your team, give everybody a few minutes to gather their input. After this, shortly go over everything that’s on the board and add a few notes where needed in order to have everybody understand the content that is on the board. Group item(s) when they are related or referring to the same underlying meaning.
After this, start discussing the most important item(s) in detail. You can use dot voting to determine the most important thing(s) if needed.
While having the discussion on a topic, always focus on what’s within the control of the team. Don’t focus too much on external people or factors, but mainly on the things that are within the control of the team to identify improvement actions that the team is able to take. You want to have 1 – 2 action items at the end of the retrospective that you can implement in the next iteration(s). Remember: you will not always have big live changing action items in each retrospective. That’s also not the intention. A small action that brings a small improvements is already very good. Try to improve a little each sprint instead of trying to bring big changes at once.
About last retrospective...
A crucial part of the retrospective is to reflect on the outcome of the previous one! Teams often forget to do this, but it is very important as it gives the team the confirmation that the action items are actually important… And that we want to make sure we improve! There is a section on the top of the template where you can refer to the action items of the last retrospective. Go over them, see how you are doing in regards to them, and decide what to do next.
Rate your retro!
At the very end of the retrospective, I ask the team to quickly rate their retrospective with focus on:
- Did we have a good discussion? Did we speak openly, and respect each others opinion?
- Do we have valuable action items? And, are we confident that we will do them in the next sprint?
We also use a feedback wall where team members can share their feedback on the retrospective. As the facilitator, you can incorporate this feedback into the next retrospective session.
Other things about the format
On the very top of the format, you can see 2 elements:
- Action items / experiments: this is the place where you would write down the action items during the retrospective. This makes it easy to summarize them at the end of the session.
- Idea for the next retrospective: I always like to foresee an area where people can give feedback or give input for the next retrospective. This can be feedback on the current format, ideas for a new format, tips, general feedback… Anything that can help us make the next retrospective even better! I would not make it required for people to give input in this, make them feel free to give input when they come up with something.
Download the template (for free)
You can download the Miro template for free below:
If you don’t have a premium version of Miro, you can also download the picture at the top of the screen and create the board in Google Drawings.