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

Constellation - Opening (#52)

Let the participants affirm or reject statements by moving around
Source: Lyssa Adkins via Luis Goncalves
Place a circle or sphere in the middle of a free space. Let the team gather around it. Explain that the circle is the center of approval: If they agree to a statement they should move towards it, if they don't, they should move as far outwards as their degree of disagreement. Now read out statements, e.g.
  • I feel I can talk openly in this retrospective
  • I am satisfied with the last iteration
  • I am happy with the quality of our code
  • I think our continuous integration process is mature
Watch the constellations unfold. Ask questions about people's observations, such as which constellations were surprising.
This can also be a closing activity (#53).

Tell me something I don’t know (#133)

Reveal everyone's hidden knowledge with a game show
Source: Adapted by Kai Alexander Lohr
Instruct participants as follows: ‘There’s a game show called ‘Tell me something I don’t know’. In it a guest states a fact, poses a related question and then the hosts ask questions in order to guess the right answers.

Here’s an example: ‘In the US you always sing along to the national anthem. In Spain no one does. Can you guess why?’ The hosts ask questions such as ‘Does it have to do with the Franco era?’, ‘Are the lyrics in a foreign language e.g. Latin?’ etc. They either guess the answer or the guest reveals it (‘The Spanish anthem doesn’t have any lyrics’).

We’re going to play this game now. Each of you will be the guest once with all the others asking questions. Reflect on the past iteration. Use the next 5 minutes to think of a fact and question.’

The fact has to fulfill 3 criteria. Write them down on a board or reveal a pre-written flipchart:
  1. It must be something that only you know and most other team members don’t know (or are unaware of)
  2. It must be worth knowing
  3. It must be actionable, i. e. have the potential to spark anything along the lines of "Let's do more/less of this.", "Watch out this doesn't happen to you.", "That was awesome. Do try it yourself.", ...
Let them write down their fact on an index card. When everyone is ready, ask the first participant to hang up their index card on the board and present their fact and question to the audience. (People who feel uncomfortable with the game flair don’t have to ask a question. They can also just tell the story around their fact without questions from the ‘audience’.) The audience asks questions to guess the answer. Short discussions are okay. The Scrum Master may also ask questions and gently steer the conversation towards possible actions. Document any actions identified during the discussion on the board. Then move on to the next participant. Use about 5 minutes per participant.

Once all the facts have been presented, the team dot-votes which fact fulfilled the 3 criteria best. The winner receives a framed “Certificate of impressive knowledge”. It documents that “$name has impressed $team with their impressive knowledge”.

The facts and actions can be input for "Generate insight" or use the actions for "Decide what to do”.

Speed Dating (#26)

Each team member explores one topic in depth in a series of 1:1 talks
Source: Thorsten Kalnin
Each participant writes down one topic they want to explore, i.e. something they'd like to change. Then form pairs and spread across the room. Each pair discusses both topics and ponders possible actions - 5 minutes per participant (topic) - one after the other. After 10 minutes the pairs break up to form new pairs. Continue until everyone has talked to everyone else.
If the group has an odd number of members, the facilitator is part of a pair but the partner gets all 10 minutes for their topic.

(The way to make all the pairings come out even is the following: Form two rows facing each other. This is pairing one. Pick one person. This person's position is fixed the entire time. Everybody else rotates one spot after each pairing.)

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.

Appreciations (#15)

Let team members appreciate each other and end positively
Source: Agile Retrospectives who took it from 'The Satir Model: Family Therapy and Beyond'
Start by giving a sincere appreciation of one of the participants. It can be anything they contributed: help to the team or you, a solved problem, ...Then invite others and wait for someone to work up the nerve. Close, when no one has talked for a minute.

(#)


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.