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

Check out the Mega Template
Retromat.org – by Corinna Baldauf
Plan-ID:
Replaced by JS
◄
Set the stage

Three Words (#82)

Everybody sums up the last iteration in 3 words
Source: Yurii Liholat
Ask everyone to describe the last iteration with just 3 words. Give them a minute to come up with something, then go around the team. This helps people recall the last iteration so that they have some ground to start from.
►
◄
Gather data

Analyze Stories (#5)

Walk through each story handled by the team and look for possible improvements
Source: Corinna Baldauf
Preparation: Collect all stories handled during the iteration and bring them along to the retrospective.
In a group (10 people max.) read out each story. For each one discuss whether it went well or not. If it went well, capture why. If not discuss what you could do differently in the future.

Variants: You can use this for support tickets, bugs or any combination of work done by the team.
►
◄
Generate insights

Park Bench (#41)

Group discussion with varying subsets of participants
Source: Diana Larsen
Place at least 4 and at most 6 chairs in a row so that they face the group. Explain the rules:
  • Take a bench seat when you want to contribute to the discussion
  • One seat must always be empty
  • When the last seat is taken, someone else must leave and return to the audience
Get everything going by sitting on the 'bench' and wondering aloud about something you learned in the previous phase until someone joins. End the activity when discussion dies down.
This is a variant of 'Fish Bowl'. It's suited for groups of 10-25 people.
►
◄
Decide what to do

Low Hanging Fruit (#63)

Visualize promise and ease of possible courses of actions to help pick
Source: Tobias Baldauf
Reveal a previously drawn tree. Hand out round index cards and instruct participants to write down the actions they would like to take - one per card. When everyone's finished, collect the cards, shuffle and read them out one by one. Place each 'fruit' according to the participants' assessment:
  • Is it easy to do? Place it lower. Hard? More to the top.
  • Does it seem very beneficial? Place it more to the left. Value is dubious at best? To the right.
The straightforward choice is to pick the bottom left fruit as action items. If this is not consensus, you can either have a short discussion to agree on some actions or dot vote.
►
◄
Close the retrospective

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.