Difference between revisions of "Retrospective meeting"

From Pearl Language
Jump to navigation Jump to search
(→‎Sources: += LeanKit » Chris Hefley » How to Run Effective Standups and Retrospectives)
 
(15 intermediate revisions by the same user not shown)
Line 1: Line 1:
*{{p|retrospective prime directive}}
==Retrospective structure==
Any meeting deserves a good structure. A default structure for a retrospective meeting looks like:
#'''Set The Stage'''—to get everyone’s attention in the room (flaps down!)
#'''Gather Data'''—to get everyone on the same page (just the facts, no feelings)
#'''Generate Insights'''—to find out what hurts most
#'''Decide What To Do'''—to implement one single improvement item
#'''Close The Retrospective'''—to collect improvement actions for next retrospective


==Retrospective Questions==
==How Navy Seals evolve using After-Action Reviews==
 
The Navy Seals only use three questions to review missions. Their breakthrough, and how it will radically improve your performance: AARs (After-Action Reviews) review projects, missions, training exercises or any other event you want to reflect on. There’s a world of difference between an effective AAR and a post-mortem bitch session. '''The magic is in the phrasing of the questions.'''
 
Here’s how to do them:
 
# '''What Went Well'''—Start every AAR by asking '''What replicable new learning did we gain from what went well?'''. In any post-mortem, our brains can naturally focus on what went wrong. However, it is critical to get clear on what went ''right'' so the good can be repeated.
# '''What Did Not Go Well'''—Next, move on to constructive criticism. Frame the conversation with a similar question: '''What replicable new learning did we gain from what did ''not'' go well?''' Note that the question isn’t asking what went wrong, but specifically what is the new '''lesson''' we can incorporate in our future behavior.
 
# '''New Standards'''—Finally, combine the insights from the first two steps, and assess the following: Drawing upon questions 1 and 2, '''what changes can we make to our processes to systematically improve our consistent excellence?'''
 
This reinforces that the standard is excellence, clear process is how we get there, and asks what improvements to our process move us ahead?
 
* Each participant should complete these questions in writing ''24 hours in advance''.
* AAR sessions begin with reading all of the written feedback.
* Then the meeting owner leads the discussion of each question.
 
With excellence as the standard:
# What went well—'''keep doing'''
# What lessons exist from what didn’t go well—'''stop doing'''
# How will we modify our processes going forward—'''change doing'''
 
==Default retrospective==
===Set the stage===
#Two truths and a lie.
#Reiterate the {{p|retrospective prime directive}}.
 
===Gather data===
#Present outcomes of previous improvement actions.
#Present standard data like:
#*Average cycle or lead time.
#*Average throughput.
#*Predictability.
#*Changes in team composition and/or availability.
#Create a timeline of the period under review; list the days of each week (Mon–Fri).
#Collect events that happened. This is neutral, objective data, e.g.
#*Mon: start using the new server
#*Tue: deployed five stories
#*Wed: had a beer
#*…
#Create three swim lanes as timeline
#*Set tick marks for every day.
#*Create four typical swim lanes:
#**neutral :-|
#**mad X-(
#**sad :-(
#**glad :-)
#*Optional: add lanes for the other two emotions:
#**afraid 8-[
#**guilty ^_^;
#Collect facts & feelings: events and observations in appropriate swim lane, cluster at will.
 
===Generate insights===
#Create table with three columns:
##Good—behavior and practices you want to hone.
##Bad—behavior and practices you want to improve.
##Ugly—behavior and practices you want to stop.
===Decide what to do===
#Split table into top and bottom halves, thus creating six cells in total:
##Top: Me/We (within team's scope).
##Bottom half: They (beyond team's scope).
#Generate measurable actions and goals in each of the six cells.
#Order them—when will you take action on which improvement item?
#Use the Good to try and fix the Bad and Ugly.
 
===Close the retrospective===
#Help, Hinder Hypothesis; or
#ROTI.
#+/Delta
 
==Retrospective questions==
*What went well?
*What went well?
*What can be improved?
*What can be improved?
Line 28: Line 104:
*How has the team worked with facilitators before?
*How has the team worked with facilitators before?


 
==Keep your retros fresh==
==Notes==
===Refreshing===
*Also conduct {{p|retrospective meeting}}s at other times than in between {{p|sprints}}.
*Also conduct {{p|retrospective meeting}}s at other times than in between {{p|sprints}}.
*Consider to ‘{{p|good bad ugly}}’ them, and physically crushing the ‘bad’ and ‘ugly’ after having collected them, and then ‘{{p|perfection game}}’ the ‘good’.
*Consider to ‘{{p|good bad ugly}}’ them, and physically crushing the ‘bad’ and ‘ugly’ after having collected them, and then ‘{{p|perfection game}}’ the ‘good’.
Line 36: Line 110:
*Turn the focus outward and ask yourself, “What can we give back to our environment?”
*Turn the focus outward and ask yourself, “What can we give back to our environment?”


==Alternative Retrospective==
==Alternative retrospective Format==
Pick two of these three key focal points in mind for every retrospective:
Pick two of these three key focal points in mind for every retrospective:
*speed;
*speed;
*fun; and
*fun; and
*quality.
*quality.
===Set the stage===
#Two truths and a lie.
===Gather data===
#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 :-|
#Collect events and observations in appropriate swim lane, cluster at will.
===Generate insights===
#Create table with three columns:
##Good—behavior and practices you want to hone.
##Bad—behavior and practices you want to improve.
##Ugly—behavior and practices you want to stop.
===Decide what to do===
#Split table into top and bottom halves, thus creating six cells in total:
##Top: Me/We (within team's scope).
##Bottom half: They (beyond team's scope).
@Generate measurable actions and goals in each of the six cells.
@Prioritize when
#Use the Good to try and fix the Bad and Ugly.
===Close the retrospective===
#Help, Hinder Hypothesis; or
#ROTI.
#+/Delta


==Sources==
==Sources==
*{{book|Agile Retrospectives|Making Good Teams Great|Esther Derby, Diana Larsen}}
*{{book|Agile Retrospectives|Making Good Teams Great|Esther Derby, Diana Larsen}}
*{{web|url=http://www.infoq.com/news/2014/01/hypotheses-retrospectives|site=InfoQ|person=Ben Linders|title=Adding Purpose and Hypotheses to Agile Retrospectives}}
{{WebSourceListItem
*{{web|url=http://www.infoq.com/news/2014/02/retrospective-actions-done|site=InfoQ|person=Ben Linders|title=Having Actions Done from Retrospectives}}
|url=https://m.signalvnoise.com/the-9-questions-that-uncover-the-most-surprising-insights-from-employees-b7bc0d20ede8
*http://www.targetprocess.com/blog/2010/11/development-practice-retrospectives-in-kanban.html
|site=Signal v. Noise
|person=Claire Lew
|title=The 9 questions that uncover the most surprising insights from employees
}}
{{WebSourceListItem
|url=http://www.infoq.com/articles/rising-continuous-retrospective
|site=InfoQ
|person=Shane Hastie
|title=Linda Rising on Continuous Retrospectives
}}
{{WebSourceListItem
|url=http://www.agilecafe.org/story-cubes-build-your-story-with-cubes-in-the-next-retrospective/
|site=Agile Cafe
|person=Omar Bermudez
|title=Story cubes: Build your story with cubes in the next retrospective
}}
{{WebSourceListItem
|url=https://masteringtheobvious.wordpress.com/2015/03/17/rollin-rollin-rollin-using-story-cubes-to-jazz-up-team-retrospectives/
|site=Mastering the Obvious
|person=Ellen Grove
|title=Rollin’ Rollin’ Rollin': Using Story Cubes to jazz up team retrospectives
}}
{{WebSourceListItem
|url=http://www.infoq.com/news/2014/01/hypotheses-retrospectives
|site=InfoQ
|person=Ben Linders
|title=Adding Purpose and Hypotheses to Agile Retrospectives
}}
{{WebSourceListItem
|url=http://www.infoq.com/news/2014/02/retrospective-actions-done
|site=InfoQ
|person=Ben Linders
|title=Having Actions Done from Retrospectives
}}
{{WebSourceListItem
|url=http://www.targetprocess.com/blog/2010/11/development-practice-retrospectives-in-kanban.html
|site=Target Process
|person=Michael Dubakov
|title=Development practice: Retrospectives in Kanban
}}
{{WebSourceListItem
|url=http://sethgodin.typepad.com/seths_blog/2015/08/self-cleaning.html
|site=Seth’s Blog
|person=Seth Godin
|title=Self cleaning
}}
{{WebSourceListItem
{{WebSourceListItem
|url=http://www.infoq.com/minibooks/agile-retrospectives-value
|url=http://www.infoq.com/minibooks/agile-retrospectives-value
Line 93: Line 184:
|title=How to Run Effective Standups and Retrospectives
|title=How to Run Effective Standups and Retrospectives
}}
}}
 
{{WebSourceListItem
 
|url=http://sethgodin.typepad.com/seths_blog/2014/12/whats-next.html
|site=Seth’s Blog
|person=Seth Godin
|title=What’s next?
}}
{{tag|kanban}}
{{tag|kanban}}
{{tag|retrospective}}
{{tag|retrospective}}
{{tag|ritual}}
{{tag|ritual}}

Latest revision as of 16:13, 15 November 2023

Retrospective structure

Any meeting deserves a good structure. A default structure for a retrospective meeting looks like:

  1. Set The Stage—to get everyone’s attention in the room (flaps down!)
  2. Gather Data—to get everyone on the same page (just the facts, no feelings)
  3. Generate Insights—to find out what hurts most
  4. Decide What To Do—to implement one single improvement item
  5. Close The Retrospective—to collect improvement actions for next retrospective

How Navy Seals evolve using After-Action Reviews

The Navy Seals only use three questions to review missions. Their breakthrough, and how it will radically improve your performance: AARs (After-Action Reviews) review projects, missions, training exercises or any other event you want to reflect on. There’s a world of difference between an effective AAR and a post-mortem bitch session. The magic is in the phrasing of the questions.

Here’s how to do them:

  1. What Went Well—Start every AAR by asking What replicable new learning did we gain from what went well?. In any post-mortem, our brains can naturally focus on what went wrong. However, it is critical to get clear on what went right so the good can be repeated.
  2. What Did Not Go Well—Next, move on to constructive criticism. Frame the conversation with a similar question: What replicable new learning did we gain from what did not go well? Note that the question isn’t asking what went wrong, but specifically what is the new lesson we can incorporate in our future behavior.
  1. New Standards—Finally, combine the insights from the first two steps, and assess the following: Drawing upon questions 1 and 2, what changes can we make to our processes to systematically improve our consistent excellence?

This reinforces that the standard is excellence, clear process is how we get there, and asks what improvements to our process move us ahead?

  • Each participant should complete these questions in writing 24 hours in advance.
  • AAR sessions begin with reading all of the written feedback.
  • Then the meeting owner leads the discussion of each question.

With excellence as the standard:

  1. What went well—keep doing
  2. What lessons exist from what didn’t go well—stop doing
  3. How will we modify our processes going forward—change doing

Default retrospective

Set the stage

  1. Two truths and a lie.
  2. Reiterate the retrospective prime directive.

Gather data

  1. Present outcomes of previous improvement actions.
  2. Present standard data like:
    • Average cycle or lead time.
    • Average throughput.
    • Predictability.
    • Changes in team composition and/or availability.
  3. Create a timeline of the period under review; list the days of each week (Mon–Fri).
  4. Collect events that happened. This is neutral, objective data, e.g.
    • Mon: start using the new server
    • Tue: deployed five stories
    • Wed: had a beer
    • …
  5. Create three swim lanes as timeline
    • Set tick marks for every day.
    • Create four typical swim lanes:
      • neutral :-|
      • mad X-(
      • sad :-(
      • glad :-)
    • Optional: add lanes for the other two emotions:
      • afraid 8-[
      • guilty ^_^;
  6. Collect facts & feelings: 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).
  2. Generate measurable actions and goals in each of the six cells.
  3. Order them—when will you take action on which improvement item?
  4. Use the Good to try and fix the Bad and Ugly.

Close the retrospective

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

Retrospective 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)?
  • What did this iteration produce?
  • What was the team aiming for?
  • How did the result meet (or not meet) expectations?
  • What’s going on elsewhere in the organization that affects the team as they go into the retrospective?
    • For example, are there rumors of layoffs?
    • Has there been a recent merger?
    • A canceled product?
  • What is the history of previous project reviews?
    • What happened?
    • What was the follow-up?
  • What are the relationships between team members?
    • How is their work interdependent?
    • What are their personal connections and working relationships?
  • What are team members feeling?
    • What are their concerns or anxieties?
    • What are they excited about?
  • What kind of outcome will achieve value for the time invested— both for the retrospective sponsor and the team?
  • How has the team worked with facilitators before?

Keep your retros fresh

  • 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 Format

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

  • speed;
  • fun; and
  • quality.

Sources

Retrieved from "http://pearllanguage.org/index.php?title=Retrospective_meeting&oldid=3046"