Planning your next agile retrospective? Start with a random plan, change it to fit the team's situation, print it and share the URL. Or browse around for new ideas!

Is this your first retrospective? Start here!

Preparing your first remote retrospective? This might help.
There's a new Retromat book geared towards beginners!

Check out "Plans for Retrospectives"

(Looking for the Print Retromat?)
Plan-ID:
Replaced by JS

What kind of X? (#140)

Participants give a metaphor for the iteration
Source: Unknown via Corinna Baldauf
Start by asking "If this iteration were an X, what kind of X would it be?" This question has endless variations from "If the iteration were a animal, what animal would it be?" over cocktails and furniture to plants and "If the iteration were a car, what car would it be?"

Ask everybody to write down their answer on a sticky note. Go around the team, everybody reads out their note and posts it on a board. Briefly discuss the answers. After all it's a difference if the iteration were "a BMW, but the brakes don't work" or a "red 2004 Toyota Prius". What does it mean to the people who wrote it down?

Analyze Stories (#5)

Walk through each story handled by the team and look for possible improvements
Source: Corinna Baldauf
Preparation: Collect all stories handled during the iteration and bring them along to the retrospective.
In a group (10 people max.) read out each story. For each one discuss whether it went well or not. If it went well, capture why. If not discuss what you could do differently in the future.
Variants: You can use this for support tickets, bugs or any combination of work done by the team.

5 Whys (#8)

Drill down to the root cause of problems by repeatedly asking 'Why?'
Source: Agile Retrospectives
Divide the participants into small groups (<= 4 people) and give each group one of the top identified issues. Instructions for the group:
  • One person asks the others 'Why did that happen?' repeatedly to find the root cause or a chain of events
  • Record the root causes (often the answer to the 5th 'Why?')
Let the groups share their findings.

Chaos Cocktail Party (#61)

Actively identify, discuss, clarify and prioritize a number of actions
Source: Suzanne Garcia via Malte Foegen
Everyone writes one card with an action that they think is important to do - the more specific (SMART), the better. Then team members go around and chat about the cards like in a cocktail party. Every chat pair discusses the actions on their two cards. Stop the chatting after 1 minute. Each chat pair splits 5 points between the two cards. More points go to the more important action. Organize 3 to 5 rounds of chats (depending on group size). At the end everyone adds up the points on their card. In the end the cards are ranked by points and the team decides how much can be done in the next iteration, pulling from the top.

Addendum: In many settings you might want to randomly switch the cards in the beginning and between discussions. In this way, neither of the point splitting parties has a stake in which of the cards gets more points. This is an idea by Dr. Sivasailam “Thiagi” Thiagarajan via Paul Tevis

Feedback Door - Numbers (ROTI) (#14)

Gauge participants' satisfaction with the retro on a scale from 1 to 5 in minimum time
Source: ALE 2011, Corinna Baldauf
Put sticky notes on the door with the numbers 1 through 5 on them. 1 is the topmost and best, 5 the lowest and worst.When ending the retrospective, ask your participants to put a sticky to the number they feel reflects the session. The sticky can be empty or have a comment or suggestion on it.

(#)


Source:
Retromat contains 127 activities, allowing for 8349005 combinations (25x30x22x22x23+5) and we are constantly adding more.

Created by Corinna Baldauf

Corinna wished for something like Retromat during her Scrummaster years. Eventually she just built it herself in the hope that it would be useful to others, too. Any questions, suggestions or encouragement? You can email her or follow her on Twitter. If you like Retromat you might also like Corinna's blog and her summaries on Wall-Skills.com.

Co-developed by Timon Fiddike

Timon gives Scrum Trainings. As Integral Coach and Agile Coach he coaches executives, managers, product owners and scrum masters. He has used Retromat since 2013 and started to build new features in 2016. You can email him or follow him on Twitter. Photo © Ina Abraham.