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.

Proud & Sorry (#33)

What are team members proud or sorry about?
Source: Agile Retrospectives
Put up two posters labeled 'proud' and 'sorry'. Team members write down one instance per sticky note. When the time is up have everyone read out their note and post it to the appropriate poster.
Start a short conversation e.g. by asking:
  • Did anything surprise you?
  • What patterns do you see? What do they mean for you as a team?

Wish granted (#50)

A fairy grants you a wish - how do you know it came true?
Source: Lydia Grawunder & Sebastian Nachtigall
Give participants 2 minutes to silently ponder the following question: 'A fairy grants you a wish that will fix your biggest problem at work overnight. What do you wish for?' Follow up with: 'You come to work the next morning. You can tell, that the fairy has granted your wish. How do you know? What is different now?' If trust within the group is high, let everyone describe their 'Wish granted'-workplace. If not, just tell the participants to keep their scenario in mind during the next phase and suggest actions that work towards making it real.

Problem Solving Tree (#96)

Got a big goal? Find the steps that lead to it
Source: Bob Sarni, described by Karen Greaves
Hand out sticky notes and markers. Write the big problem you want to solve onto a note and stick it to the top of a wall or big board. Ask the participants to write down ideas of what they can do to solve the problem. Post them one level below the original problem. Repeat this for each note on the new level. For every idea ask whether it can be done in a single iteration and if everyone understands what they need to do. If the answer is no, break it down and create another level in the problem solving tree.

Once you have lower levels that are well understood and easy to implement in a single iteration, dot vote to decide which to tackle in the next iteration.

Note to Self (#104)

Remind yourself of your good intentions
Source: Fun Retrospectives
Thinking back about the discussions, everybody writes a reminder for her- or himself about a change in their own behaviour they want to try during the next iteration. It's for quiet self reflection and is not shared with the group. They take their respective sticky notes with them to their desktop and put it in a place they will look at often.

(#)


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.