Blog | Books | 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.
Run great agile retrospectives: Get all activities and more for your ebook reader!

Check out the Retromat ebook!

(Looking for the Print Retromat?)
Replaced by JS

Emoticon Project Gauge (#32)

Help team members express their feelings about a project and address root causes early
Source: Andrew Ciccarelli
Prepare a flipchart with faces expressing various emotions such as:
  • shocked / surprised
  • nervous / stressed
  • unempowered / constrained
  • confused
  • happy
  • mad
  • overwhelmed
Let each team member choose how they feel about the project. This is a fun and effective way to surface problems early. You can address them in the subsequent phases.

Quartering - Identify boring stories (#64)

Categorize stories in 2 dimensions to identify boring ones
Source: Wayne D. Grant
Draw a big square and divide it into 2 columns. Label them 'Interesting' and 'Dull'. Let the team write down everything they did last iteration on stickies and put it into the appropriate column. Have them add a rough estimate of how long it took on each of their own stickies.
Now add a horizontal line so that your square has 4 quadrants. Label the top row 'Short' (took hours) and the bottom row 'Long' (took days). Rearrange the stickies in each column.
The long and dull stories are now nicely grouped to 'attack' in subsequent phases.

(Splitting the assessment into several steps, improves focus. You can adapt Quartering for lots of other 2-dimensional categorizations.)

Cause-Effect-Diagram (#25)

Find the source of problems whose origins are hard to pinpoint and lead to endless discussion
Source: Henrik Kniberg
Write the problem you want to explore on a sticky note and put it in the middle of a whiteboard. Find out why that is a problem by repeatedly asking 'So what?'. Find out the root causes by repeatedly asking 'Why (does this happen)?' Document your findings by writing more stickies and showing causal relations with arrows. Each sticky can have more than one reason and more than one consequence
Vicious circles are usually good starting points for actions. If you can break their bad influence, you can gain a lot.

Dot Voting - Keep, Drop, Add (#38)

Brainstorm what behaviors to keep, drop & add and pick the top initiatives
Source: Agile Retrospectives
Divide a flip chart into boxes headed with 'Keep', 'Drop' and 'Add'. 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.

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.