• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Team Driven Improvement with Retrospectives

Team Driven Improvement with Retrospectives



Talk "Team Driven Improvement with Retrospectives" given at London Scrum User Group on 18th October 2012.

Talk "Team Driven Improvement with Retrospectives" given at London Scrum User Group on 18th October 2012.



Total Views
Views on SlideShare
Embed Views



3 Embeds 90

https://twitter.com 86
http://tweetedtimes.com 3
http://www.slashdocs.com 1



Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

    Team Driven Improvement with Retrospectives Team Driven Improvement with Retrospectives Presentation Transcript

    • Team-drivenImprovement with RetrospectivesRachel.Davies@UnrulyMedia.com Twitter: @rachelcdavies
    • Agile Coach @ Unruly
    • Who’s Here?
    • Enjoy working in a team?Enjoyed working in a team?
    • Team-driven!
    • FrustrationsSometimes teamwork isdifficult ..
    • Sustainable pace?
    • “Retrospective?” “Retrospective?” • Looking back over a lifetime of work?
    • Project RetrospectivesPioneered  by  Norman  Kerth.“a  ritual  held  at  the  end  of  a  project  to learn  from  the  experience  and  to  plan changes  for  the  next  effort.”Book:  Project  Retrospec:ves explains  techniques  for  3  day  off-­‐site  mee:ngs  at the  end  of  a  project  to  iden:fy  lessons  learned.
    • Retrospectives A meeting where a team looks back on a past period of work so that they can learn from their experience and apply this learning to future work.
    • Safety Check
    • Project Timeline
    • Mining The Time Line for GoldUse flip-chart to categorize experience• What has worked well?• What have we learned?• What to do differently?• What is still puzzling?• What needs further work?
    • “A discussion ofwhat went right andwhat went wrong inthe Sprint, andwhat can be doneto improve the nextSprint.” 2004
    • Typical Scrum RetrospectiveCut-down list of questions• What went well?• What didn’t go well?• Actions Risk: team judge past events rather than thinking how to react next time around!
    • Disconnected Cycle?SMPO £££
    • Agile Retrospective CycleFrom “Agile Retrospectives”by Derby & Larsen
    • Pitfalls
    • No time to improve!
    • Living in the past Spend too much on looking back, no time to discuss future changes.
    • Unconnected Ideas Individuals have ideas for improvement but don’t connect them to team action.
    • Cloudy Thinking If team is not clear on what to do then nothing happens
    • Thinking too big! Be realistic! How much can you really do next sprint?
    • No owner When no one on team champions a change, it gets forgotten
    • Always the Same Owner Scrum Master takes on actions for the team rather than supporting team to do actions themselves.
    • Invisible Actions Actions from retrospective not visible to team or outside.
    • Activities that trivialise
    • Picking on people Maintain safety
    • Tips
    • Meetings require pre-workand follow up! Hard to learn about creating effective retrospective by being a participant
    • Care for People• Make a safe space• Diffuse tension• Bring food and drinks
    • Slow Down!• People will not talk if you do not listen to them• Invite everyone to share what happened• Take time to gather the whole story• Involve each member of the team• Forget about making lists of what went well, etc.
    • Apply Scrum planning• Break down into improvementgoal and action steps smallenough to fit into sprint cycle• Prioritise along with other work• Review in Scrum meetings
    • Rotate theFacilitator
    • Experiment!• Retrospectives are about learning from experience• Experiment and adapt the format to generate new insights
    • Is there an elephant in theroom? Acknowledge the current state
    • Drop the Timebox?• Try running your retrospective without a timebox.• If there’s not much to talk about finish early• If there’s a lot to talk about it keep going (with plenty of breaks)
    • Get Outside• Get out of the office• Go to the park or the pub• Lifts pressure and generates energy• Remember to take notes and photos
    • Be patient Change Takes Time
    • References• Project Retrospectives: A Handbook for Team Reviews by Norman L. Kerth.• Agile Retrospectives: Making Good Teams Great by Esther Derby & Diana Larsen.• The Retrospective Handbook by Patrick Kua• Collaboration Explained by Jean Tabaka.• Agile Coaching by Rachel Davies & Liz Sedley.• Facilitator’s Guide to Participatory Decision-Making by Sam Kaner• Innovation Games by Luke Hohmann• http://facstaff.unca.edu/manns/retropatterns.html• http://www.retrospectives.com• http://www.retrospectivefacilitatorgathering.org/• http://xp123.com/xplor/xp0509/index.shtml
    • Any Questions?
    • Thank you!