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.]
Categorize stories in 2 dimensions to identify boring ones Source:
Wayne D. Grant
Draw a big square and divide it into 2 columns. Label them 'Interesting' and 'Dull'. Let the team write down everything they did last iteration on stickies and put it into the appropriate column. Have them add a rough estimate of how long it took on each of their own stickies. Now add a horizontal line so that your square has 4 quadrants. Label the top row 'Short' (took hours) and the bottom row 'Long' (took days). Rearrange the stickies in each column. The long and dull stories are now nicely grouped to 'attack' in subsequent phases.
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.
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.