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

Weather Report (#2)

Participants mark their 'weather' (mood) on a flipchart
Source: Agile Retrospectives
Prepare a flipchart with a drawing of storm, rain, clouds and sunshine. Each participant marks their mood on the sheet.

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

5 Whys (#8)

Drill down to the root cause of problems by repeatedly asking 'Why?'
Source: Agile Retrospectives
Divide the participants into small groups (<= 4 people) and give each group one of the top identified issues. Instructions for the group:
  • One person asks the others 'Why did that happen?' repeatedly to find the root cause or a chain of events
  • Record the root causes (often the answer to the 5th 'Why?')
Let the groups share their findings.

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

Helped, Hindered, Hypothesis (#16)

Get concrete feedback on how you facilitated
Source: Agile Retrospectives
Prepare 3 flip chart papers titled 'Helped', 'Hindered', and 'Hypothesis' (suggestions for things to try out). Ask participants to help you grow and improve as a facilitator by writing you sticky notes and signing their initials so that you may ask questions later.

(#)


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.