The document provides a simple recipe for running effective Agile retrospectives. The recipe involves 6 steps: OPEN IT to get people engaged at the start, 'STORM IT' to gather topics for discussion, FILTER IT to identify key discussion topics, ANALYSE IT to get to the root causes of issues, (TO) DO IT to define actions, and CLOSE IT to summarize actions and look for improvements. Various techniques are suggested for each step, and tips are provided for facilitators to keep retrospectives focused, timed and productive. Additional resources for running retrospectives are also referenced.
3. From the Agile manifesto:
At regular intervals, the team reflects on how to
become more effective, then tunes and adjusts
its behaviour accordingly.
“I like them because stuff changes afterwards”
Barbara Gruber
4. Retrospective fatigue
Have you noticed…
people are unfocused
there is a lack of buy in
follow through is bad
participation is poor
the insights gained are not useful
5. Make it interesting
Follow a simple recipe, flavour as needed
OPEN IT ‘STORM IT FILTER IT ANALYSE IT (TO) DO IT CLOSE IT
6. Open it
Goal: Get people involved and engaged in the first 5
minutes. Trigger memories about the sprint/cycle just been.
Ways to do it: fist of five ESVP
weather report quick question
temp reading constellation three words
7. ‘storm it
Goal: Gather data from team members, so that we can
choose good topics to talk about.
Ways to do it: stop start change mad sad glad
the 4 Ls peaks & valleys
draw a timeline hot air balloon speed boat
8. Filter it
Goal: Identify the topics that the team would like to talk
about.
Ways to do it: dot vote plus minus voting
round of applause
vote with your feet circles in the soup
9. Analyse it
Goal: Get to the root cause of the issue.
Ways to do it: 5 whys lean coffee
speed dating
written brainstorming
what would awesome
look like? (And why
aren’t we there yet
10. (To) do it
Goal: write up 2 or 3 SMART, owned actions to be resolved
in the next sprint/cycle.
Ways to do it: by the team or verbatim.
11. Close it
Goal: Sum up your actions, check for opportunities to
improve your next retrospective.
Ways to do it: however you opened the retrospective,
close it that way too.
12. There, you’ve done it!
How can a retrospective be boring with this recipe?
OPEN IT ‘STORM IT FILTER IT ANALYSE IT (TO) DO IT CLOSE IT
13. Tips for facilitators
Be neutral
Keep to time
Focus on what you can change
One or two things at once Use sharpies
Post actions close to your board, check regularly
‘Park it’
Stay in the background
14. Further resources
Fun retrospectives: http://www.funretrospectives.com/
Tasty Cupcakes: http://tastycupcakes.org/?s=retrospectives&x=0&y=0
Retromat: http://plans-for-retrospectives.com/
Retrospective Wiki: http://retrospectivewiki.org/index.php?title=Retrospective_Plans
Recommended books/purchases
Agile Retrospectives: Making Good Teams Great by Esther Derby: http://www.amazon.com/Agile-
Retrospectives-Making-Teams-Great/dp/0977616649
Retromat in print format: http://plans-for-retrospectives.com/print/index.html
Retrospective Coaching Cards: http://www.amazon.com/Retrospective-Coaching-Cards-Geoff-
Watts/dp/0957587473/
Agile Kaizen: Managing Continuous Improvement Far Beyond Retrospectives by by Angel Medinilla:
http://www.amazon.com/Agile-Kaizen-Continuous-Improvement-Retrospectives/dp/364254990X/
Retrospect it! by Peti Morgan is licensed under a Creative Commons Attribution 4.0 International License. Based on a work at
https://medium.com/agile-software-development/retrospect-it-a-simple-recipe-for-building-fun-agile-retrospectives-144f4097a1d2.
Editor's Notes
moth
manchester, before industrial revolution
peppered moth - speckled with white, and black
100 years, turned black
PROGRESS SLIDE
why?
pollution - birds
moths with more black survived
natural selection
adapted to environment
white moth ok elsewhere
teams need to adapt to changing environment
we must play mother nature, take care of natural selection
not team members - but processes and behaviours!
retrospectives
from the agile manifesto
timebox for our evolution
in simpler words (Barbara)
PROGRESS SLIDE
nothing new, we know WHY
but have you noticed…
why is this happening?
retros BORING
PROGRESS SLIDE
attention span?
5 minutes
bullshit - 30 seconds
brain autopilots - done before? autopilot
won’t get good participation, insights, actions
self perpetuating cycle
good retros with zombies?
make it interesting
6 distinct parts to a retro can flavour?
PROGRESS SLIDE
never facilitate or attend same retro again!
going to walk through each step - goal, some suggestions (further resources)
open it
get them engaged - first 5 minutes
think about the way they are contributing
trigger memories
PROGRESS SLIDE
few ways: fist of five, line up, weather report.
ESVP a good one explorer shopper vacationer prisoner
explorer: keen, want to contribute to improving processesshopper: open to seeing what opportunities arisevacationer: pleased to be away from desk, maybe not contribute so muchprisoner: here against will, don’t want to contribute
explorers shoppers ideal
vacationers prisoners, want to change
prisoner - opportunity to leave, or share why
many prisoners? focus retro on that
some people change minds
maybe 5 minutes, unless problem
brainstorming
writing on post its bit
facts, data information
5 - 10 minutes, easy if memories triggered in opening
can still do targeted - set theme
PROGRESS SLIDE
many many ways
flavour with abandon
filter it - so can focus
PROGRESS SLIDE
few minutes at most
basic ingredient
focus on what can change
how else?
now have popular topics, time to dig in
get to the root cause, understand elements of why
ask powerful questions
PROGRESS SLIDE
one person dominates conversation? losing valuable insights
try written brainstorming to draw the quiet ones out
or work in pairs
Got good insights, now for action
What elements make a good action?
SMART (specific, measurable, achievable, relevant and timely)
PROGRESS SLIDE
agreed on by team
owned by a person
good time to sum up
opportunities to improve
culture of honesty - if you didn’t enjoy it, OWN it
PROGRESS SLIDE
can close the same way you opened
ESVP - where did you end up
temp reading - has it changed?
reaffirm the value of having the retro
there’s the recipe
opportunities to flavour, address problems, get people more engaged,
KEEP IT INTERESTING
It’s up to you
PROGRESS SLIDE EACH PARA
be neutral - external facilitator?
timebox, but flexible within
focus on what you CAN change
one or two things at once
sharpies, not biros
actions visible and close to board, check often
park divergent topics, or bleating
what would you want your facilitator to know?