Retromat: Facilitator's Tools: Post Mortem: 129-7-8-96-144

◄

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.

►

◄

Gather data

Mad Sad Glad (#7)

Collect events when team members felt mad, sad, or glad and find the sources
Source: Agile Retrospectives

Put up three posters labeled 'mad', 'sad', and 'glad' (or >:(, :(, :) alternatively). Team members write down one event per color coded card, when they've felt that way. When the time is up have everyone post their cards to the appropriate posters. Cluster the cards on each poster. Ask the group for cluster names.
Debrief by asking:

What's standing out? What's unexpected?
What was difficult about this task? What was fun?
What patterns do you see? What do they mean for you as a team?
Suggestions on how to continue?

►

◄

Generate insights

5 Whys (#8)

Drill down to the root cause of problems by repeatedly asking 'Why?'
Source: Agile Retrospectives

Divide the participants into small groups (<= 4 people) and give each group one of the top identified issues. Instructions for the group:

One person asks the others 'Why did that happen?' repeatedly to find the root cause or a chain of events
Record the root causes (often the answer to the 5th 'Why?')

Let the groups share their findings.

►

◄

Decide what to do

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.

►

◄

Close the retrospective

Elevenie (#144)

Write a short poem
Source: Stefanie Dinh

An Elevenie (German 'Elfchen') is a poem with 11 words on five lines – 1, 2, 3, 4 and 1 word per line respectively. Only do this with a team in which people enjoy working with each other. It's a wonderful activity to do with a team that is disbanding at the end of a project as a way to commerate the good times.

Hand out pens and paper and read out the instructions:
'We are going to each write a poem with 5 lines. Each line has a specific number of words. Don't worry, I'll guide you through each line, one by one. Write down 1 word that comes to mind when you think about our team (a feeling, a color, ...).
On the next line, describe this feeling with 2 words.
On the next line, add details with 3 words – What is it like? How does it smell or sound? What would you like to add?
On line 4, write down a sentence with 4 words, starting with 'I'. What do you associate with your feeling.
Take a moment to read your poem thus far. What 1 word comes to mind? This is the final word of your poem on line 5.'

Now you can go around and everybody who wants to, can read out their poem. Bring tissues, it can be quite moving.

►

String Theory (#129)

Mad Sad Glad (#7)

5 Whys (#8)

Problem Solving Tree (#96)

Elevenie (#144)

(#)

Created by Corinna Baldauf

Co-developed by Timon Fiddike