1. The document discusses how to run effective retrospectives (retros) for agile teams and provides examples of bad, good, and great retro techniques.
2. Examples of bad retros include being unprepared, not having clear facilitation, allowing blaming sessions, and not defining follow-up actions. Good retros are prepared, well-facilitated, enforce positive behavior, and define clear actions.
3. Great retro techniques provided as examples include appreciative retrospectives, emotional timelines, the 4 L's (liked, learned, lacked, longed for), Lean Coffee, and Jeopardy. Each technique has specific instructions provided.
How to Jazz up your Retros - Agile BA Meetup - Melbourne - 08/04/14
1. 1
How to jazz up
your Retros
Ryan McKergow
Twitter: @RMcKergow
LinkedIn: RyanMcKergow
Special thanks to:
Image
source:
h"p://www.jazzeddie.f2s.com/images/Simpsons/lisabeatnikkid.gif
2. 2
Overview
• A quick intro to Retros
• How to run a:
1. Bad Retro – How can they go wrong
2. Good Retro - Areas to address in your Retros
3. Great Retro – New & disruptive Retro techniques
4. 4
“Agile Retrospectives are special
meetings where a team steps back,
examines the way they work, and
identifies ways they can improve.”
Ester Derby
5. 5
How to run a bad Retro
Image
source:
h"p://www.berryreview.com/wp-‐content/uploads/2007/10/student.gif
11. 11
How to run a good Retro
Image
source:
h"p://countersoe.wpengine.netdna-‐cdn.com/wp-‐content/uploads/2013/12/REtrospecHve-‐meeHng-‐lego-‐640x360.png
18. 18
Instructions:
• Start by providing another team member with positive feedback
– As a team, reflect on the past Iteration. What were the:
• Strengths
• Successes
• Major events
– Discuss the reflections together
– Repeat the process thinking about the next two Iterations
– Discuss the reflections together
– Work out an action plan to achieve the team’s future state
• Find out more about the Appreciative Retrospective here:
http://retrospectivewiki.org/index.php?title=Appreciative_Retrospective
Appreciative Retrospective
20. 20
Instructions:
• Draw a time line on a whiteboard
• Ask the team to write down:
– Good events
– Problematic events
– Significant events
• Explain the events for context
• Everyone plots how happy or sad they were throughout the timeline
• Plot out the consensus line for the team
• Discuss the findings and identify actions for improvement in the future
• Find out more about the Emotional Timeline Retrospective here:
http://www.agileacademy.com.au/agile/sites/default/files/Timeline
%20Retropectives%202011.pdf
Emotional Timeline
22. 22
Instructions:
• Reflect on 4 different categories:
– Liked
– Learned
– Lacked
– Longed for
• Write notes against each category
• Split into 4 even teams
• Each team goes through findings and presents to everyone
• Discuss important topics with team
• Agree on action items
• Find out more about the 4 L's Retrospective here:
http://ebgconsulting.com/blog/the-4l%E2%80%99s-a-retrospective-technique/
The 4 L’s Retro
24. 24
Instructions:
• Ask everyone to raise 1-2 topics for discussion
• Vote on the discussion items
• Start discussion about the topic for 5 minutes
• After 5 minutes, vote on whether to continue discussions
• Throughout the discussions, identify actions to take away
• Find out more about the Lean Coffee Retrospective here:
http://www.agilecafe.org/lean-coffee-retrospective/
Lean Coffee
26. 26
Instructions:
• Draw a Jeopardy game board
• Everyone writes a one word or short phrase answer
• Think of the question to the answer. Don’t tell anyone.
• The team guesses the question to the answer
• Discuss where the questions are different to owner’s question
• Agree on actions from the discussions
• Find out more about the Jeopardy Retrospective here:
http://retrospectivewiki.org/index.php?title=Jeopardy_Retrospective
Jeopardy
28. 28
Instructions:
• Team draws:
– a Boat (Your team)
– some Wind pushing the boat forward (Activities/behaviours/processes that could give the
team moment)
– an Anchor holding the boat back (What is currently hold us back from achieving our goals)
– an Iceberg in the distance (What is something that could really damage the team in the
future)
• Team writes notes against the three elements impacting the boat
• Read out notes to team
• Group into themes (optional)
• Discuss the findings
• Identify actions from the notes
• Find out more about the Speedboat Retrospective here:
http://innovationgames.com/speed-boat/
Speedboat
29. 29
Recap
How to run a:
1. Bad Retro – How can they go wrong
2. Good Retro - Areas to address in your Retros
3. Great Retro – New & disruptive Retro techniques