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.
Walk through each story handled by the team and look for possible improvements Source:
Preparation: Collect all stories handled during the iteration and bring them along to the retrospective. In a group (10 people max.) read out each story. For each one discuss whether it went well or not. If it went well, capture why. If not discuss what you could do differently in the future. Variants: You can use this for support tickets, bugs or any combination of work done by the team.
'Imagine you could time travel to the end of the next iteration (or release). You learn that it was the best, most productive iteration yet! How do your future selves describe it? What do you see and hear?' Give the team a little time to imagine this state and jot down some keywords to aid their memory. Then let everyone describe their vision of a perfect iteration. Follow up with 'What changes did we implement that resulted in such a productive and satisfying future?'Write down the answers on index cards to use in the next phase.
Divide a flip chart into boxes headed with 'Start', 'Continue' and 'Stop'. Ask your participants to write concrete proposals for each category - 1 idea per index card. Let them write in silence for a few minutes. Let everyone read out their notes and post them to the appropriate category. Lead a short discussion on what the top 20% beneficial ideas are. Vote on it by distributing dots or X's with a marker, e.g. 1, 2, and 3 dots for each person to distribute. The top 2 or 3 become your action items.
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.