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

How’s your battery? (#143)

Check in on everybody’s well-being
Source: Anh Bui
If your phone battery runs low you look for a charger. With human beings it is harder to tell when they need to recharge. That’s why we use this activity to ask explicitly: Prepare a flipchart by outlining one battery per participant.

Ask each participant to color in their battery to show how much energy they currently have. Reflect together on the results, e. g. by asking “What do you notice?” – especially if someone is low on energy (“What would help you save or even gain energy?”)

Depending on how much time you want to invest you can do rounds of collecting and reflecting on:
  • What costs you energy at work?
  • What gives you energy?
  • What can you do to gain energy – short-term / long-term?

Room Service (#139)

Take a look at the team room: Does it help or hinder?
Source: Corinna Baldauf
This activity works best if you hold the retrospective where (most of) the team work.

On a whiteboard, post 2 headlines: 'Our work space helps me/us ...' and 'Our work space makes it hard to ...'.

Give participants 5 minutes to write their individual answers on sticky notes – 1 idea per note. Afterwards go around the group and let everyone post their answers in the respective categories. Allow for a short discussion, e.g. using Lean Coffee (#51).

If the team have not suggested any actions without a prompt, close with 'Based on everyone's answers, what would you like to change about your setup?' to come up with action items.

Snow Mountain (#118)

Address problematic burndowns and scope creep
Source: Olivier Fortier
This activity is helpful when a team is constantly dealing with additional requests and scope creep. Use the burndown chart of problematic sprints to draw snowy mountains with the same outline. Add a few trees here and there. Print drawings of kids in various sledging situations such as kid sledging down fast, kid sledging and being scared, kid with a sledge looking bored, etc. (You can use Google image search with 'kid sledging drawing').

In teams of 2 or 3, ask the team members to identify which kid's reaction goes with which part of the mountain.
Example: If the mountain is flat, the kid might be bored. If you're facing a wall, the kid might be scared.

You can then discuss the team's reaction facing their own burndowns.

Merge (#21)

Condense many possible actions down to just two the team will try
Source: Lydia Grawunder & Sebastian Nachtigall
Hand out index cards and markers. Tell everyone to write down the two actions they want to try next iteration - as concretely as possible (SMART). Then everyone pairs up with their neighbor and both together must merge their actions into a single list with two actions. The pairs form groups of 4. Then 8. Now collect every group's two action items and have a vote on the final two.

Feedback Door - Smilies (#23)

Gauge participants' satisfaction with the retro in minimum time using smilies
Source: Boeffi
Draw a ':)', ':|', and ':(' on a sheet of paper and tape it against the door. When ending the retrospective, ask your participants to mark their satisfaction with the session with an 'x' below the applicable smily.

(#)


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.