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.

Laundry Day (#98)

Which things are clear and feel good and which feel vague and implicit?
Source: Katrin Dreyer
Use this activity if you suspect the team to make lots of unconscious decisions hardly ever questioning anything. You can figure out what things need to be talked about to get an explicit grasp of them.

You need:
  • about 3 metres of string as the clothesline
  • about 20 clothes pins
  • a white shirt (cut from paper)
  • a pair of dirty pants (cut from paper)
Hang up the clothesline and mark the middle, e.g. with a ribbon. Hang up the clean shirt on one side and the dirty pants on the other. Ask the team now to write items onto index cards for each of the two categories: 'Clean - Clear and well understood' and 'Dirty - Unclear and confusing'. Hang up the notes with clothespins and re-arrange them into clusters. Now the team picks 2 'dirty' and 2 'clean' topics they want to talk about, e.g. by dot voting.

If I were you (#95)

What could sub-groups improve when interacting with others?
Source: Thomas Wallet
Identify sub-groups within the participants that interacted during the iteration, e.g. developers/testers, clients/providers, PO/developers, etc. Give participants 3 minutes to silently write down what they think their group did that negatively impacted another group. One person should be part of one group only and write stickies for all groups they don't belong to - 1 sticky per issue.

Then in turn all participants read their stickies and give them to the corresponding group. The affected group rates it from 0 ('It was not a problem') to 5 ('It was a big problem'). Thus you get insights and shared understanding about problems and can select some of them to work on.

Circles & Soup / Circle of Influence (#29)

Create actions based on how much control the team has to carry them out
Source: Diana Larsen who adapted it from 'Seven Habits of Highly Effective People' by Stephen Covey and Circle of Influence and Concern' by Jim Bullock
Prepare a flip chart with 3 concentric circles, each big enough to put stickies in. Label them 'Team controls - Direct action', 'Team influences - Persuasive/recommending action' and 'The soup - Response action', from innermost to outermost circle respectively. ('The soup' denotes the wider system the team is embedded into.) Take your insights from the last phase and put them in the appropriate circle.
The participants write down possible actions in pairs of two. Encourage them to concentrate on issues in their circle of influence. The pairs post their action plans next to the respective issue and read it out loud. Agree on which plans to try (via discussion, majority vote, dot voting, ...)

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.