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.
Visualize how information flows in, out and around the team Source:
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?
Group discussion with varying subsets of participants Source:
Place at least 4 and at most 6 chairs in a row so that they face the group. Explain the rules:
Take a bench seat when you want to contribute to the discussion
One seat must always be empty
When the last seat is taken, someone else must leave and return to the audience
Get everything going by sitting on the 'bench' and wondering aloud about something you learned in the previous phase until someone joins. End the activity when discussion dies down. This is a variant of 'Fish Bowl'. It's suited for groups of 10-25 people.
Asking and answering go around the team circle - an excellent way to reach consensus Source:
Everyone sits in a circle. Begin by stating that you'll go round asking questions to find out what you want to do as a group. You start by asking your neighbor the first question, e.g. 'What is the most important thing we should start in the next iteration?' Your neighbor answers and asks her neighbor a related question. Stop when consensus emerges or the time is up. Go around at least once, so that everybody is heard!
Gauge participants' satisfaction with the retro on a scale from 1 to 5 in minimum time Source:
ALE 2011, Corinna Baldauf
Put sticky notes on the door with the numbers 1 through 5 on them. 1 is the topmost and best, 5 the lowest and worst.When ending the retrospective, ask your participants to put a sticky to the number they feel reflects the session. The sticky can be empty or have a comment or suggestion on it.