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

Round of Admiration (#76)

Participants express what they admire about one another
Source: Judith Andresen
Start a round of admiration by facing your neighbour and stating 'What I admire most about you is ...' Then your neighbour says what she admires about her neighbour and so on until the last participants admires you. Feels great, doesn't it?

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.

Pessimize (#74)

If we had ruined the last iteration what would we have done?
Source: Judith Andresen
You start the activity by asking: 'If we had completely ruined last iteration what would we have done?' Record the answers on a flip chart. Next question: 'What would be the opposite of that?' Record it on another flip chart. Now ask participants to comment the items on the 'Opposite'-chart by posting sticky notes answering 'What keeps us from doing this?'. Hand out different colored sticky notes to comment on the comments, asking 'Why is it like this?'.

Landscape Diagram (#100)

Assess action items based on how clear they are and take your pick
Source: Diana Larsen adapted it from Human Systems Dynamics Institute
This activity is helpful when a team is facing an ambiguous, volatile, uncertain or complex set of problems and has many suggested action items to choose from.

Draw a Landscape Diagram, i.e. an x-axis labeled 'Certainty about approach' and a y-axis labeled 'Agreement on issue'. Both go from low certainty / agreement in their mutual origin to high towards the top / right. For each action item ask 'How much agreement do we have that solving this problem would have a great beneficial impact? How certain are we about the first steps toward a solution?' Place the note on the diagram accordingly.
When all actions are placed, shortly discuss the 'map' you created. Which actions will give the greatest benefit in the next iteration? Which are more long term?

Choose 2 actions from the simple / ordered area of the map or 1 action from the complex area.

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.