Walk through each story handled by the team and look for possible improvements Source: Corinna Baldauf
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.
Find the source of problems whose origins are hard to pinpoint and lead to endless discussion Source: Henrik Kniberg
Write the problem you want to explore on a sticky note and put it in the middle of a whiteboard. Find out why that is a problem by repeatedly asking 'So what?'. Find out the root causes by repeatedly asking 'Why (does this happen)?' Document your findings by writing more stickies and showing causal relations with arrows. Each sticky can have more than one reason and more than one consequence Vicious circles are usually good starting points for actions. If you can break their bad influence, you can gain a lot.
Get a sense of everyone's position and reach consensus Source: Nick Oostvogels
When the team can't decide between two options, create a big scale (i.e. a long line) on the floor with masking tape. Mark one end as option A) and the other as option B). Team members position themselves on the scale according to their preference for either option. Now tweak the options until one option has a clear majority.
A good debriefing deepens understanding, learning and sharing. Preparation: Download and assemble the Debriefing Cube and cards.
During the retrospective, roll the cube. Then draw a card from the category it shows and use it to prompt a discussion. Repeat as time permits.
This will broaden your debriefing options and is especially great for groups without a facilitator to enable them to effectively debrief on their own.