Retromat: Scrum Retrospective Experiment: 129-139-118-24-16

◄

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

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.

►

◄

Generate insights

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.

►

◄

Decide what to do

Open Items List (#24)

Participants propose and sign up for actions
Source: Corinna Baldauf, inspired by this list

Prepare a flip chart with 3 columns titled 'What', 'Who', and 'Due'. Ask one participant after the other, what they want to do to advance the team. Write down the task, agree on a 'done by'-date and let them sign their name.
If someone suggests an action for the whole team, the proposer needs to get buy-in (and signatures) from the others.

►

◄

Close the retrospective

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.

►

String Theory (#129)

Room Service (#139)

Snow Mountain (#118)

Open Items List (#24)

Helped, Hindered, Hypothesis (#16)

(#)

Created by Corinna Baldauf

Co-developed by Timon Fiddike