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!
Are you running your retrospectives with Miro? Create prettier boards faster with the giant Retromat Miroboard Mega Template!

Check out the Mega Template
Plan-ID:
Replaced by JS

Check In - Draw the Iteration (#31)

Participants draw some aspect of the iteration
Source: Corinna Baldauf, adapted from Thorsten Kalnin, Olivier Gourment; Thomas Guest
Distribute index cards and markers. Set a topic, e.g. one of the following:
  • How did you feel during the iteration?
  • What was the most remarkable moment?
  • What was the biggest problem?
  • What did you long for?
  • If the last iteration had been a circus performance, what part did you play? Juggler, funambulist, clown, knife-thrower, ...
Ask the team members to draw their answer. Post all drawings on a whiteboard. For each drawing let people guess what it means, before the artist explains it.
Metaphors open new viewpoints and create a shared understanding.

Hit the Headlines (#119)

Which sprint events were newsworthy?
Source: Thomas Guest
Collect some news headlines in advance and take them to the retrospective to serve as examples. Try to gather a mixture of headlines: factual, opinion, review. Place the headlines where everyone can see them. Hand out sticky notes. Give team members 10 minutes to come up with their own headlines describing newsworthy aspects of the sprint. Encourage short, punchy headlines.
Stick the completed headlines to a whiteboard. If any cover the same news item, combine them. If any are unclear, ask the reporter for details. Vote on which news items to discuss and analyse in more depth.

Company Map (#68)

Draw a map of the company as if it was a country
Source: Judith Andresen
Hand out pens and paper. Pose the question 'What if the company / department / team was territory? What would a map for it look like? What hints would you add for save travelling?' Let participants draw for 5-10 minutes. Hang up the drawings. Walk through each one to clarify and discuss interesting metaphors.

Planning Poker Voting (#99)

Use your Planning Poker cards for un-influenced voting
Source: Andreas Ratsch
If you've got very influential and / or shy team members you can re-use Planning Poker cards to vote simultaneously:

Write all suggested actions on sticky notes and put them onto a wall. Hand out an ordered deck of Planning Poker cards to each participant. Count the proposals and remove that many cards from the back of the card decks. If you've got 5 suggestions you might have cards '1', '2', '3', '5', and '8'. This depends on your deck (some have a '1/2' card). It doesn't matter, as long as all participants have the same set of values.

Explain the rules: Choose a card for each suggestion. Choose a low value if the action is not worth doing in your opinion. Choose a high value if the action is worth starting next iteration.

Give them a minute to sort out their internal ranking and then present the first suggested action. Everybody chooses a card and they reveal them at the same time. Add the numbers from all cards and write the sum onto the action. Remove the used poker cards. Repeat this for all actions. If you have more actions than poker values the players can show 'no card' (counting 0) for the appropriate number of times.

Implement the action with the highest sum in the next iteration. Add more actions only if there's team consensus to do so.

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. He mentors advanced scrum masters and advanced product owners. Human, dad, nerd, contact improv & tango dancer. 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.