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.]
Imagine your last iteration was a movie and write a review about it Source:
Introduce the activity by asking: Imagine your last iteration was a movie and you had to write a review:
What was the genre of the movie (e.g. horror, drama, ...)?
What was the (central) theme? Describe in 2-3 words.
Was there a big twist (e.g. a bad guy)?
What was the ending like (e.g. happy-end, cliffhanger) and did you expect it?
What was your personal highlight?
Would you recommend it to a colleague?
Give each team member a piece of paper and 5 minutes to silently ponder the questions. In the meantime (or before the session) divide a flip chart in 7 columns headed with 'Genre', 'Theme', 'Twist', 'Ending', 'Expected?', 'Highlight', 'Recommend?'. When everyone has finished writing, fill out the flip chart while each participant reads out their notes. Afterwards look at the finished table and lead a discussion about
What's standing out?
What patterns do you see? What do they mean for you as a team?
What could sub-groups improve when interacting with others? Source:
Identify sub-groups within the participants that interacted during the iteration, e.g. developers/testers, clients/providers, PO/developers, etc. Give participants 3 minutes to silently write down what they think their group did that negatively impacted another group. One person should be part of one group only and write stickies for all groups they don't belong to - 1 sticky per issue.
Then in turn all participants read their stickies and give them to the corresponding group. The affected group rates it from 0 ('It was not a problem') to 5 ('It was a big problem'). Thus you get insights and shared understanding about problems and can select some of them to work on.
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.