Retrospective meeting

• retrospective prime directive

Questions:

• What went well?
• What can be improved?
• What have we learned?
• What do we still not know?
• What still puzzles us?
• What wishes do we have?
• Which single experiment will we do (to speed up)?

Sources

• http://www.targetprocess.com/blog/2010/11/development-practice-retrospectives-in-kanban.html

Notes

Refreshing

• Also conduct retrospective meetings at other times than in between sprints.
• Consider to ‘good bad ugly’ them, and physically crushing the ‘bad’ and ‘ugly’ after having collected them, and then ‘perfection game’ the ‘good’.
• tip top each other, just like a temperature reading. Top identifies something you value in the other. Tip is a request—petition, solicitation, prayer, desire—for specific behavior of the other.
• Turn the focus outward and ask yourself, “What can we give back to our environment?”

Alternative Retrospective

Pick two of these three key focal points in mind for every retrospective:

• speed;
• fun; and
• quality.

Set the stage

1. Two truths and a lie.

Gather data

1. Create three swim lanes as timeline, tick marks for every week; glad, neutral, sad are typical; you can also opt for the basic five emotions + neutral, so six swim lanes in total:
   • mad X-(
   • sad :-(
   • glad :-)
   • afraid 8-[
   • guilty ^_^;
   • neutral :-|
2. Collect events and observations in appropriate swim lane, cluster at will.

Generate insights

1. Create table with three columns:
   1. Good—behavior and practices you want to hone.
   2. Bad—behavior and practices you want to improve.
   3. Ugly—behavior and practices you want to stop.

Decide what to do

1. Split table into top and bottom halves, thus creating six cells in total:
   1. Top: Me/We (within team's scope).
   2. Bottom half: They (beyond team's scope).

@Generate measurable actions and goals in each of the six cells. @Prioritize when

1. Use the Good to try and fix the Bad and Ugly.

Close the retrospective

1. Help, Hinder Hypothesis; or
2. ROTI.
3. +/Delta