Everyone in the team states their goal for the retrospective, i.e. what they want out of the meeting. Examples of what participants might say:
I'm happy if we get 1 good action item
I want to talk about our argument about unit tests and agree on how we'll do it in the future
I'll consider this retro a success, if we come up with a plan to tidy up $obscureModule
[You can check if these goals were met if you close with activity #14.]
[The Meet - Core Protocol, which inspired this activity, also describes 'Alignment Checks': Whenever someone thinks the retrospective is not meeting people's needs they can ask for an Alignment Check. Then everyone says a number from 0 to 10 which reflects how much they are getting what they want. The person with the lowest number takes over to get nearer to what they want.]
Each participant tells a story about the last iteration that contains certain words Source:
Provide everyone with something to write down their story. Then introduce the shaping words, which influence the story to be written:
If the last iteration could have been better: You set a couple of shaping words, e.g. such as 'mad, sad, glad' or 'keep, drop, add'. Additionally they have to write their story in first person. This avoids blaming others.
If the last iteration was successful: The team can either choose their own set of words or you can provide random words to unleash the team's creativity.
Now each participant writes a story of no more than 100 words about last iteration. They have to use each shaping word at least once. Timebox this to 5-10 minutes. When everyone's finished, they read out their stories. Afterwards lead a discussion about common themes of the stories.
'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.
Condense many possible actions down to just two the team will try Source:
Lydia Grawunder & Sebastian Nachtigall
Hand out index cards and markers. Tell everyone to write down the two actions they want to try next iteration - as concretely as possible (SMART). Then everyone pairs up with their neighbor and both together must merge their actions into a single list with two actions. The pairs form groups of 4. Then 8. Now collect every group's two action items and have a vote on the final two.
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.