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

Who said it? (#106)

Attribute quotes to team members and situations
Source: Beccy Stafford
Before the retro, spend some time looking through email threads, chat logs, ticket discussions, and the like. Collect quotes from the last iteration: Funny quotes, or quotes which without context sound a little odd. Write them down with the name of the person who said them.

Read out the quotes at the beginning of the retro, and ask the team to guess who said it - the source may not self-identify! Often the team will not only know who said it, but also talk about what was going on at the time.

The Good, the Bad, and the Ugly (#121)

Collect what team members perceived as good, bad and non-optimal
Source: Manuel Küblböck
Put up three sections labeled ‘The Good’, ‘The Bad’ and ‘The Ugly’. Give everyone 5 minutes to note down one or more things per category from the last sprint. One aspect per post-it. When the time is up, have everyone stick their post-its to the appropriate labels. Cluster as you collect, if possible.

Poster Session (#91)

Split a large group into smaller ones that create posters
Source: Unknown, adapted by Corinna Baldauf, inspired by Michal Grzeskowiak
After you've identified an important topic in the previous phase you can now go into detail. Have the larger group split up into groups of 2-4 people that will each prepare a poster (flip chart) to present to the other groups. If you have identified more than one main topic, let the team members select on which they want to work further.
Give the teams guidelines about what the posters should cover / answer, such as:
  • What exactly happens? Why is that a problem?
  • Why / when / how does this situation happen?
  • Who benefits from the current situation? What is the benefit?
  • Possible solutions (with Pros and Cons)
  • Who could help change the situation?
  • ... whatever is appropriate in your setting ...
The groups have 15-20 minutes to discuss and create their posters. Afterwards gather and each group gets 2 minutes to present their results.

Merge (#21)

Condense many possible actions down to just two the team will try
Source: Lydia Grawunder & Sebastian Nachtigall
Hand out index cards and markers. Tell everyone to write down the two actions they want to try next iteration - as concretely as possible (SMART). Then everyone pairs up with their neighbor and both together must merge their actions into a single list with two actions. The pairs form groups of 4. Then 8. Now collect every group's two action items and have a vote on the final two.

Feedback Door - Numbers (ROTI) (#14)

Gauge participants' satisfaction with the retro on a scale from 1 to 5 in minimum time
Source: ALE 2011, Corinna Baldauf
Put sticky notes on the door with the numbers 1 through 5 on them. 1 is the topmost and best, 5 the lowest and worst.When ending the retrospective, ask your participants to put a sticky to the number they feel reflects the session. The sticky can be empty or have a comment or suggestion on it.

(#)


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.