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

Agile Values Cheer Up (#90)

Remind each other of agile values you displayed
Source: Jesus Mendez
Draw 4 large bubbles and write one of the agile core values into each:
  1. Individuals and their interactions
  2. Delivering working software
  3. Customer collaboration
  4. Responding to change
Ask participants to write down instances when their colleagues have displayed one of the values - 1 cheerful sticky note per example. In turn, let everyone post their note in the corresponding bubble and read them out loud. Rejoice in how you embody agile core values :)

Roles and Responsibilities (#146)

Clarify expectations and responsibilities for each role on the team
Source: Role-Up
Many conflicts arise from unclear expectations. Talking about individual people can feel like an attack. That’s why this activity focusses on expectations towards roles.

Create a table with one column per role in the team. (Limit it to 7 columns. If there are more than 7 roles, leave out roles that have little conflict.) The rows of the table are: 

  • Role name
  • This role is responsible for …
  • This role is NOT responsible for …
Leave enough space between the bottom rows so that people who aren’t sure whether something is a role’s responsibility have an unofficial inbetween space to post them. Hand out pens, as well as yellow and orange sticky notes.

Ask everyone to write yellow sticky notes listing the responsibilities for each role – 1 responsibility per note. Set a timer for 8 minutes and read the room to see if you can stop early or have to give more time. Post all the sticky notes but don’t discuss them yet.

Repeat this process with the non-responsibilities on orange sticky notes.

The team now dot-vote on which topics they want to talk about. Give enough time to read all the sticky notes and distribute 7 votes.

Start with the topic with the most votes. Invite the people who voted for it to share why they want to talk about it. Try to clarify expectations team members have about a role’s responsibilities. Write down clarifications or agreements the team make. Repeat for the next highest voted topic until time runs out.

If I were you (#95)

What could sub-groups improve when interacting with others?
Source: Thomas Wallet
Identify sub-groups within the participants that interacted during the iteration, e.g. developers/testers, clients/providers, PO/developers, etc. Give participants 3 minutes to silently write down what they think their group did that negatively impacted another group. One person should be part of one group only and write stickies for all groups they don't belong to - 1 sticky per issue.

Then in turn all participants read their stickies and give them to the corresponding group. The affected group rates it from 0 ('It was not a problem') to 5 ('It was a big problem'). Thus you get insights and shared understanding about problems and can select some of them to work on.

Planning Poker Voting (#99)

Use your Planning Poker cards for un-influenced voting
Source: Andreas Ratsch
If you've got very influential and / or shy team members you can re-use Planning Poker cards to vote simultaneously:

Write all suggested actions on sticky notes and put them onto a wall. Hand out an ordered deck of Planning Poker cards to each participant. Count the proposals and remove that many cards from the back of the card decks. If you've got 5 suggestions you might have cards '1', '2', '3', '5', and '8'. This depends on your deck (some have a '1/2' card). It doesn't matter, as long as all participants have the same set of values.

Explain the rules: Choose a card for each suggestion. Choose a low value if the action is not worth doing in your opinion. Choose a high value if the action is worth starting next iteration.

Give them a minute to sort out their internal ranking and then present the first suggested action. Everybody chooses a card and they reveal them at the same time. Add the numbers from all cards and write the sum onto the action. Remove the used poker cards. Repeat this for all actions. If you have more actions than poker values the players can show 'no card' (counting 0) for the appropriate number of times.

Implement the action with the highest sum in the next iteration. Add more actions only if there's team consensus to do so.

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.