Everybody sums up the last iteration in 3 words Source:
Ask everyone to describe the last iteration with just 3 words. Give them a minute to come up with something, then go around the team. This helps people recall the last iteration so that they have some ground to start from.
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.
Brainstorm what behaviors to keep, drop & add and pick the top initiatives Source:
Divide a flip chart into boxes headed with 'Keep', 'Drop' and 'Add'. Ask your participants to write concrete proposals for each category - 1 idea per index card. Let them write in silence for a few minutes. Let everyone read out their notes and post them to the appropriate category. Lead a short discussion on what the top 20% beneficial ideas are. Vote on it by distributing dots or X's with a marker, e.g. 1, 2, and 3 dots for each person to distribute. The top 2 or 3 become your action items.
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.