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!
Are you running your retrospectives with Miro? Create prettier boards faster with the giant Retromat Miroboard Mega Template!

Check out the Mega Template
Plan-ID:
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.

Story Oscars (#54)

The team nominates stories for awards and reflects on the winners
Source: Marin Todorov
Display all stories completed in the last iterations on a board. Create 3 award categories (i.e. boxes on the board):
  • Best story
  • Most annoying story
  • ... 3rd category invented by the team ...
Ask the team to 'nominate' stories by putting them in one of the award boxes.
For each category: Dot-vote and announce the winner. Ask the team why they think the user story won in this category and let the team reflect on the process of completing the tasks - what went good or wrong.

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?

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. He mentors advanced scrum masters and advanced product owners. Human, dad, nerd, contact improv & tango dancer. 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.