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

Appreciative Goal (#36)

State an affirmative goal for the session
Source: Diana Larsen
Concentrate on positive aspects instead of problems by setting an affirmative goal, e.g.
  • Let's find ways to amplify our strengths in process and teamwork
  • Let's find out how to extend our best uses of engineering practices and methods
  • We'll look at our best working relationships and find ways to build more relationships like that
  • We'll discover where we added the most value during our last iteration to increase the value we'll add during the next

Meeting Satisfaction Histogram (#87)

Create a histogram on how well ritual meetings went during the iteration
Source: Fanny Santos
Prepare a flip chart for each meeting that recurs every iteration, (e.g. the Scrum ceremonies) with a horizontal scale from 1 ('Did not meet expectations') to 5 ('Exceeds Expectations'). Each team member adds a sticky note based on their rating for each of these meetings. Let the team discuss why some meetings do not have a rating of 5.
You can discuss improvements as part of this activity or in a later activity such as Perfection Game (#20) or Plus & Delta (#40).

Braver (#145)

What does courage look like? What would the team do if they were bolder?
Source: Johanna Amlacher
Put up four posters with the following questions:
  • Which person in the team do you find courageous and how does courage show itself?
  • When have you felt insecure and wished you were braver?
  • What helps you to be brave?
  • What bold idea would you try as a team if you were 10 times bolder?
For each question do a round of:
  • 4 minutes of quiet time to answer the question on sticky notes
  • Ask people to read out and post their answers. (In a large group you can use 1-2-4-All to discuss answers in smaller groups first.)
  • Cluster similar answers
(We do it in several rounds to slowly warm up the participants to tackle the last question.)

After the last round, look at all the answers and facilitate a discussion. Ask participants what is standing out for them? What's unexpected? What patterns do they see? What do these patterns mean for them as a team?

Then ask the team to rate themselves on a scale of 1-10: How brave do they think they are? Followed by: What would be possible if they were one step higher on the scale?

Based on everything they’ve talked about, what would they like to try that’s somewhat bold yet safe enough?

Chaos Cocktail Party (#61)

Actively identify, discuss, clarify and prioritize a number of actions
Source: Suzanne Garcia via Malte Foegen
Everyone writes one card with an action that they think is important to do - the more specific (SMART), the better. Then team members go around and chat about the cards like in a cocktail party. Every chat pair discusses the actions on their two cards. Stop the chatting after 1 minute. Each chat pair splits 5 points between the two cards. More points go to the more important action. Organize 3 to 5 rounds of chats (depending on group size). At the end everyone adds up the points on their card. In the end the cards are ranked by points and the team decides how much can be done in the next iteration, pulling from the top.

Addendum: In many settings you might want to randomly switch the cards in the beginning and between discussions. In this way, neither of the point splitting parties has a stake in which of the cards gets more points. This is an idea by Dr. Sivasailam “Thiagi” Thiagarajan via Paul Tevis

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. 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.