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

Check In - Quick Question (#3)

Ask one question that each participant answers in turn
Source: Agile Retrospectives
In round-robin each participant answers the same question (unless they say 'I pass'). Sample questions:
  • In one word - What do you need from this retrospective?
    When someone answers something that alerts you such as "help" or "protection", you have to react to that e. g. with "Is there something we can do right now to help?" oder "What kind of protection?"
  • What's something that caused problems last iteration?
  • If you could change one thing about the last iteration what would it be?

Avoid evaluating comments such as 'Great'. 'Thanks' is okay.

Agile Self-Assessment (#35)

Assess where you are standing with a checklist
Source: Corinna Baldauf
Print out a checklist that appeals to you, e.g.:Go through them in the team and discuss where you stand and if you're on the right track.
This is a good activity after an iteration without major events.

Remember the Future (#37)

Imagine the next iteration is perfect. What is it like? What did you do?
Source: Luke Hohmann, found at Diana Larsen
'Imagine you could time travel to the end of the next iteration (or release). You learn that it was the best, most productive iteration yet! How do your future selves describe it? What do you see and hear?' Give the team a little time to imagine this state and jot down some keywords to aid their memory. Then let everyone describe their vision of a perfect iteration.
Follow up with 'What changes did we implement that resulted in such a productive and satisfying future?'Write down the answers on index cards to use in the next phase.

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.

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.