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

Why Retrospectives? (#46)

Ask 'Why do we do retrospectives?'
Source: Pete Roessler
Go back to the roots and start into the retrospective by asking 'Why do we do this?' Write down all answers for everyone to see. You might be surprised.

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

Maximize Follow Through (#117)

Think about how the team will follow up and set yourselves up for success
Source: Chris Rimmer
Prepare a flip chart with 4 columns titled 'Action', 'Motivation', 'Ease' and 'Reminder'. Write down the list of actions the team wants to take in the first column. Read out each action and fill in the other columns by asking:
  • Motivation - How can we motivate ourselves to do this?
    Examples: 'Jane will own this and report back at the next retrospective', or 'We'll reward ourselves with cake on Friday if we do this every day'

  • Ease - How can we make it easy to do?
    Example: For an action 'Start involving Simon in the stand up' a possibility could be 'Move the task board next to Simon's desk'

  • Reminder - How will we remember to do this?
    Examples: 'Richard will put a reminder in Google Calendar' or 'We'll do this after the stand up each day'
Actions do not require all of the above. But if there are no suggestions for any of the columns, ask the team if they really think they will do it.

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.