Blog | Books | Membership | About
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?)
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?

Like to like (#6)

Participants match quality cards to their own Start-Stop-Continue-proposals
Source: Agile Retrospectives
Preparation: ca. 20 quality cards, i.e. colored index cards with unique words such as fun, on time, clear, meaningful, awesome, dangerous, nasty
Each team member has to write at least 9 index cards: 3 each with things to start doing, keep doing and stop doing. Choose one person to be the first judge. The judge turns the first quality card. From their own cards each member chooses the best match for this word and places it face down on the table.The last one to choose has to take their card back on their hand. The judge shuffles all submitted cards, turns them one by one and rules the best fit = winning card. All submitted cards are discarded. The submitter of the winning card receives the quality card. The person left of the judge becomes the new judge.
Stop when everyone runs out of cards (6-9 rounds). Whoever has the most quality cards wins. Debrief by asking for takeaways.
(Game is based on 'Apples to Apples')

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.

Dot Voting - Starfish (#49)

Collect what to start, stop, continue, do more and less of
Source: Pat Kua
Draw 5 spokes on a flip chart paper, dividing it into 5 segments. Label them 'Start', 'Stop', 'Continue', 'Do More' and 'Do less'. Participants write their proposals on sticky notes and put them in the appropriate segment. After clustering stickies that capture the same idea, dot vote on which suggestions to try.

Helped, Hindered, Hypothesis (#16)

Get concrete feedback on how you facilitated
Source: Agile Retrospectives
Prepare 3 flip chart papers titled 'Helped', 'Hindered', and 'Hypothesis' (suggestions for things to try out). Ask participants to help you grow and improve as a facilitator by writing you sticky notes and signing their initials so that you may ask questions later.

(#)


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.