Assess how to continue with last retro's actions Source: Sven Winkler
Create a table with 5 columns. The first column lists last retro's action items. The other columns are headed 'More of', 'Keep doing', 'Less of' and 'Stop doing'. Participants place 1 sticky note per row into the column that states how they want to proceed with that action. Afterwards facilitate a short discussion for each action, e.g. asking:
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.
Asking and answering go around the team circle - an excellent way to reach consensus Source: Agile Retrospectives
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!
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.