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.
This activity is helpful when a team is facing an ambiguous, volatile, uncertain or complex set of problems and has many suggested action items to choose from.
Draw a Landscape Diagram, i.e. an x-axis labeled 'Certainty about approach' and a y-axis labeled 'Agreement on issue'. Both go from low certainty / agreement in their mutual origin to high towards the top / right. For each action item ask 'How much agreement do we have that solving this problem would have a great beneficial impact? How certain are we about the first steps toward a solution?' Place the note on the diagram accordingly. When all actions are placed, shortly discuss the 'map' you created. Which actions will give the greatest benefit in the next iteration? Which are more long term?
Choose 2 actions from the simple / ordered area of the map or 1 action from the complex area.
Let team members appreciate each other and end positively Source:
Agile Retrospectives who took it from 'The Satir Model: Family Therapy and Beyond'
Start by giving a sincere appreciation of one of the participants. It can be anything they contributed: help to the team or you, a solved problem, ...Then invite others and wait for someone to work up the nerve. Close, when no one has talked for a minute.