Retromat: Scrum Lessons Learned Plan: 130-86-66-117-34

◄

Spot the Elephant (#130)

Are there problems nobody talks about?
Source: Willem Larsen

Prepare 1 set of cards per team member. A set of cards contains 1 elephant card, 1 boot card, 1 happy sun card, and 1 moon card. Explain how they each choose one card from their set:

If a team member thinks there is at least one 'Elephant in the room' (unspoken but important problem) for this team, then choose the Elephant card. Choosing this card doesn't mean that they have to talk about the Elephant or even say what they think the problem is.
If there are no Elephants, but they got their feelings hurt in an interaction at least once since the last retrospective (and didn't mention it), choose the Boot crushing flower card.
If everything is hunky dory for them, choose the Happy Sun.
If they're uncomfortable sharing, or don't feel like any other card fits, choose the neutral Moon.

To preserve anonymity, everyone places their chosen card face down on the feedback pile and the rest of their sets face down on a discard pile. Shuffle the discard pile to ensure anonymity and put it aside. Shuffle the feedback pile and then reveal the cards one at a time.

If your team has 1 or more Elephants in the room, you have some serious issues with psychological safety. Let the team sit with their new knowledge and offer a larger retrospective soon to make space for them to share if they wish, but do not ask directly who chose what. Preserve the anonymity and do not coerce explanations of the chosen card! This is a critical opportunity to build trust and preserve your ability to gain insight into the state of the team.

In the same way, depending on the size of your team, two or more hurt feelings suggest that you may have safety issues. Two or more Moons also suggests a lack of psychological safety. Take this feedback into consideration when designing your next retro. There are lots of great ways to more thoroughly dive into and surface learnings, this activity just points out when such a retrospective is needed.

►

◄

Gather data

Lines of Communication (#86)

Visualize how information flows in, out and around the team
Source: Tarmo Aidantausta

Is information not flowing as well as it needs to? Do you suspect bottlenecks? Visualize the ways information flows to find starting points for improvements. If you want to look at one specific flow (e.g. product requirements, impediments, ...) check out Value Stream Mapping (#79). For messier situations try something akin to Cause-Effect-Diagrams (#25).
Look at the finished drawing. Where are delays or dead ends?

►

◄

Generate insights

Brainwriting (#66)

Written brainstorming levels the playing field for introverts
Source: Prof. Bernd Rohrbach

Pose a central question, such as 'What actions should we take in the next iteration to improve?'. Hand out paper and pens. Everybody writes down their ideas. After 3 minutes everyone passes their paper to their neighbour and continues to write on the one they've gotten. As soon as they run out of ideas, they can read the ideas that are already on the paper and extend them. Rules: No negative comments and everyone writes their ideas down only once. (If several people write down the same idea, that's okay.)
Pass the papers every 3 minutes until everyone had every paper. Pass one last time. Now everyone reads their paper and picks the top 3 ideas. Collect all top 3's on a flip chart for the next phase.

►

◄

Decide what to do

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.

►

◄

Close the retrospective

Shower of Appreciation (#34)

Listen to others talk behind your back - and only the good stuff!
Source: Ralph Miarka

Form groups of 3. Each group arranges their chairs so that 2 chairs face each other and the third one has its back turned, like this: >^<. The two people in the chairs that face each other talk about the third person for 2 minutes. They may only say positive things and nothing that was said may be reduced in meaning by anything said afterwards.
Hold 3 rounds so that everyone sits in the shower seat once.

►

Spot the Elephant (#130)

Lines of Communication (#86)

Brainwriting (#66)

Maximize Follow Through (#117)

Shower of Appreciation (#34)

(#)

Created by Corinna Baldauf

Co-developed by Timon Fiddike