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

String Theory (#129)

Surface shared traits and mutual interests among team members
Source: Eben Halford
This is an excellent activity for newly formed teams of 6 to 15 members. It speeds up team building by sharing traits and interests so that team members can build closer bonds than possible with just work-related stuff.

Have the team form a circle with everyone looking inwards. Leave about a foot of space between people. Depending on what you want to stress with this activity, you can ask colleagues that usually work remotely to stand about 5 feet away from the circle.

Hand a ball of yarn to a random player and tell them to hold on tight to the end of the yarn with their non-dominant hand and the ball in the dominant one. The yarn holder starts the game by saying something about themselves that is not work-related such as 'I have a daughter' or 'I play the guitar'. If this statement is true for any other team member they raise their hand and say 'Yes, that's me'. The yarn holder passes the ball to the person who raised their hand. If there's more than one, the yarn holder can choose one. If no one shares the statement the yarn holder has to make another statement.

The person who received the ball of yarn holds on to the thread and tautens it. This is the first connection in a network of shared traits. The new yarn holder now makes a statement about themselves, passes the ball while holding on to their part of the yarn and so on.

The game ends when time is up OR everybody has at least two connections OR the yarn runs out.

You can debrief with some of these questions:
  • What did you notice?
  • If you've got remote people: How does it feel to stand apart? How does it feel to have someone stand apart?
  • How do you feel about few (or no) connections?
  • What is it like to see this web of connections?
  • Can you be a team without this web?
  • What would happen if someone let go of their threads? How would it affect the team?
  • Is there anything you will do differently at work now?

This activity is only the first part of a longer game.

Retro Wedding (#89)

Collect examples for something old, new, borrowed and blue
Source: Jordan Morris, via Todd Galloway
Analogue to an anglo-american wedding custom ask the team to give examples for the following categories:
  • Something Old
    Positive feedback or constructive criticism on established practice
  • Something New
    Positive feedback or constructive criticism on experiments in progress
  • Something Borrowed
    Tool/idea from another team, the Web or yourself for a potential experiment
  • Something Blue
    Any blocker or source of sadness
One example per sticky note. There's only one rule: If someone contributes to the 'Something Blue' column, s/he must also have a positive comment in at least 1 other column.

Everyone posts their stickies in the appropriate column on the board and describes it briefly.

Brainstorming / Filtering (#10)

Generate lots of ideas and filter them against your criteria
Source: Agile Retrospectives
Lay out the rules of brainstorming, and the goal: To generate lots of new ideas which will be filtered after the brainstorming.
  • Let people write down their ideas for 5-10 minutes
  • Go around the table repeatedly always asking one idea each, until all ideas are on the flip chart
  • Now ask for filters (e.g. cost, time investment, uniqueness of concept, brand appropriateness, ...). Let the group choose 4.
  • Apply each filter and mark ideas that pass all 4.
  • Which ideas will the group carry forward? Does someone feel strongly about one of the ideas? Otherwise use majority vote.
The selected ideas enter Phase 4.

Outside In (#124)

Turn blaming others into actions owned by the team
Source: Ralph Miarka and Veronika Kotrba
If your team has a tendency to see obstacles outside of their team and influence and primarily wants others to change, you can try this activity:

Draw a big rectangle on the board and another rectangle inside of it, like a picture frame. Hang all complaints and grievances that surfaced in previous phases into the frame.

Now comes the interesting twist: Explain that if they want anything in the outside frame to change, they will have to do something themselves to affect that change. Ask the team to come up with actions they can do. Put these actions into the inner rectangle (near the outer sticky they are addressing).

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.