Distribute index cards and markers. Set a topic, e.g. one of the following:
How did you feel during the iteration?
What was the most remarkable moment?
What was the biggest problem?
What did you long for?
If the last iteration had been a circus performance, what part did you play? Juggler, funambulist, clown, knife-thrower, ...
Ask the team members to draw their answer. Post all drawings on a whiteboard. For each drawing let people guess what it means, before the artist explains it. Metaphors open new viewpoints and create a shared understanding.
You take the DeLorean back to the beginning of the project Source:
This activity is great for looking at a longer period of time. Put on your storyteller hat and ask your team to imagine the following scenario:
"You are sitting relaxed at your computer working, when suddenly there is a loud bang and a huge cloud of dust is in your room. You cough and as the dust settles, you realize that a car has driven through the wall of your house. You approach cautiously to see what has happened. The car looks futuristic and has gullwing doors. You wipe the dust off the windshield and realize: it's Marty McFly with his DeLorean. He seems unharmed, but is unconscious. You sense your chance and gently push Marty into the passenger seat. The time machine seems to be undamaged. You risk it and travel back to the beginning of your project: Greenfield. Not a single line of code has been written yet. Now you have the possibility to start again from scratch:
What do you definitely keep?
What do you do differently this time?
What were your biggest learnings?"
Give everybody 7 minutes to write down their ideas on sticky notes – 1 idea per sticky. When the time is up, the first person briefly presents their stickies for the first category and posts them on the board for this category. Then the second person presents and so on. Cluster as you go along. What themes do appear?
If your boss had witnessed the last iteration, what would she want you to change? Source:
Imagine your boss had spent the last iteration - unrecognized - among you. What would she think about your interactions and results? What would she want you to change? This setting encourages the team to see themselves from a different angle.
Check for resistance instead of approval Source:
Georg Paulus, Siegfried Schrotta \& Erich Visotschnig via Corinna Baldauf
Do you have a hotly debated matter with several possible ways to go and the team can't agree on any of them? Instead of trying to find a majority for a way that will create winners and losers, try what happens if you turn the decision inside out: Draw a table with the voters in the left-most column and proposals on top. Now everybody has to fill in their resistance towards each proposal. 0 means 'no resistance - this is what I want', up to 10, meaning 'shoot me now'. Give the least hated solution a try.
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.