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.
Different parties present manifestos for change. Who will get your vote? Source:
Is there an election coming up in your country? Use it as a back drop for your team to convince each other of their change initiatives.
Ask the participants to split into political parties with 2 or 3 members. For 20 minutes, each party will work on a manifesto for change. What isn't working? How would they improve things? Afterwards the parties meet again and their leaders present their manifestos. Be prepared for tough questions and heckling! Now plan for a better world! Summarise the manifestos with sticky notes, one color per party. What do the parties agree on? Which promises are unrealistic and which can you achieve?
Introduce SMART goals (specific, measurable, attainable, relevant, timely) and examples for SMART vs not so smart goals, e.g.'We'll study stories before pulling them by talking about them with the product owner each Wednesday at 9am' vs. 'We'll get to know the stories before they are in our sprint backlog'. Form groups around the issues the team wants to work on. Each group identifies 1-5 concrete steps to reach the goal. Let each group present their results. All participants should agree on the 'SMART-ness' of the goals. Refine and confirm.
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.