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.
OMG! Print Retromats are back! Get yours fresh off the printer

More about the Retromat Print Edition

(Looking for the ebook?)
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.

Tell a Story with Shaping Words (#93)

Each participant tells a story about the last iteration that contains certain words
Source: Philip Rogers
Provide everyone with something to write down their story. Then introduce the shaping words, which influence the story to be written:
  • If the last iteration could have been better:
    You set a couple of shaping words, e.g. such as 'mad, sad, glad' or 'keep, drop, add'. Additionally they have to write their story in first person. This avoids blaming others.
  • If the last iteration was successful:
    The team can either choose their own set of words or you can provide random words to unleash the team's creativity.
Now each participant writes a story of no more than 100 words about last iteration. They have to use each shaping word at least once. Timebox this to 5-10 minutes.
When everyone's finished, they read out their stories. Afterwards lead a discussion about common themes of the stories.

Original 4 (#55)

Ask Norman Kerth's 4 key questions
Source: Norman Kerth
Norman Kerth, inventor of retrospectives, identified the following 4 questions as key:
  • What did we do well, that if we didn’t discuss we might forget?
  • What did we learn?
  • What should we do differently next time?
  • What still puzzles us?
What are the team's answers?

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.

Appreciations (#15)

Let team members appreciate each other and end positively
Source: Agile Retrospectives who took it from 'The Satir Model: Family Therapy and Beyond'
Start by giving a sincere appreciation of one of the participants. It can be anything they contributed: help to the team or you, a solved problem, ...Then invite others and wait for someone to work up the nerve. Close, when no one has talked for a minute.

(#)


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.