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

Check In - Amazon Review (#18)

Review the iteration on Amazon. Don't forget the star rating!
Source: Christian Heiß
Each team member writes a short review with:
  • Title
  • Content
  • Star rating (5 stars is the best)
Everyone reads out their review. Record the star ratings on a flip chart.
Can span whole retrospective by also asking what is recommended about the iteration and what not.

Movie Critic (#110)

Imagine your last iteration was a movie and write a review about it
Source: Isabel Corniche
Introduce the activity by asking: Imagine your last iteration was a movie and you had to write a review:
  • What was the genre of the movie (e.g. horror, drama, ...)?
  • What was the (central) theme? Describe in 2-3 words.
  • Was there a big twist (e.g. a bad guy)?
  • What was the ending like (e.g. happy-end, cliffhanger) and did you expect it?
  • What was your personal highlight?
  • Would you recommend it to a colleague?
Give each team member a piece of paper and 5 minutes to silently ponder the questions. In the meantime (or before the session) divide a flip chart in 7 columns headed with 'Genre', 'Theme', 'Twist', 'Ending', 'Expected?', 'Highlight', 'Recommend?'. When everyone has finished writing, fill out the flip chart while each participant reads out their notes.
Afterwards look at the finished table and lead a discussion about
  • What's standing out?
  • What patterns do you see? What do they mean for you as a team?
  • Suggestions on how to continue?

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 - Worked well, Do differently (#39)

Brainstorm what worked well & what to do differently and pick the top initiatives
Source: Agile Retrospectives
Head 2 flip charts with 'Worked well' and 'Do differently next time' respectively. Ask your participants to write concrete proposals for each category - 1 idea per index card. Let them write in silence for a few minutes. Let everyone read out their notes and post them to the appropriate category. Lead a short discussion on what the top 20% beneficial ideas are. Vote on it by distributing dots or X's with a marker, e.g. 1, 2, and 3 dots for each person to distribute. The top 2 or 3 become your action items.

SaMoLo (More of, Same of, Less of) (#17)

Get course corrections on what you do as a facilitator
Source: Fairly good practices
Divide a flip chart in 3 sections titled 'More of', 'Same of', and 'Less of'. Ask participants to nudge your behaviour into the right direction: Write stickies with what you should do more, less and what is exactly right. Read out and briefly discuss the stickies section-wise.

(#)


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.