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!
Become a Certified Scrum Master® trained by Retromat Co-Developer Timon Fiddike and Andreas Schliep – Get a 50 % price reduction for their CSM® Deluxe Training on 20-22.11.2019 in Berlin (German language). This is a unique opportunity, here's why.

Use Berlin-50% code on signup
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.

Lean Coffee (#51)

Use the Lean Coffee format for a focused discussion of the top topics
Source: Original description and in action
Say how much time you set aside for this phase, then explain the rules of Lean Coffee for retrospectives:
  • Everyone writes down topics they’d like to discuss - 1 topic per sticky
  • Put the stickies up on a whiteboard or flipchart. The person who wrote it describes the topic in 1 or 2 sentences. Group stickies that are about the same topic
  • Everyone dot-votes for the 2 topics they want to discuss
  • Order the stickies according to votes
  • Start with the topic of highest interest
  • Set a timer for 5 minutes. When the timer beeps, everyone gives a quick thumbs up or down. Majority of thumbs up: The topic gets another 5 minutes. Majority of thumbs down: Start the next topic.
Stop when the allotted time is over.

Learning Matrix (#9)

Team members brainstorm in 4 categories to quickly list issues
Source: Agile Retrospectives
After discussing the data from Phase 2 show a flip chart with 4 quadrants labeled ':)', ':(', 'Idea!', and 'Appreciation'. Hand out sticky notes.
  • The team members can add their input to any quadrant. One thought per sticky note.
  • Cluster the notes.
  • Hand out 6-10 dots for people to vote on the most important issues.
This list is your input for Phase 4.

Circle of Questions (#11)

Asking and answering go around the team circle - an excellent way to reach consensus
Source: Agile Retrospectives
Everyone sits in a circle. Begin by stating that you'll go round asking questions to find out what you want to do as a group. You start by asking your neighbor the first question, e.g. 'What is the most important thing we should start in the next iteration?' Your neighbor answers and asks her neighbor a related question. Stop when consensus emerges or the time is up. Go around at least once, so that everybody is heard!

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.