Agile Retrospectives

download Agile Retrospectives

of 24

Embed Size (px)

description

 

Transcript of Agile Retrospectives

  • Agile Retrospectives Most Things Work, Until They Dont www.allisonpollard.com
  • Allison Pollard Agile coach and consultant Firm believer in continuous improvement DFW Scrum user group leader and Dallas Agile Leadership Network board member Glasses wearer www.allisonpollard.com
  • What is a Retrospective? Hint: its not a lessons learned or a post-mortem www.allisonpollard.com
  • Why have a Retrospective? At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. --Agile Manifesto www.allisonpollard.com
  • Are your retrospectives missing something? Lack of participation www.allisonpollard.com
  • Retrospective Format www.allisonpollard.com
  • 1. Set the Stage Establish the focus for the retrospective Establish or re-purpose working agreements Set other concerns aside [for now] Engage team members early so they participate Photo by Alan Dayley www.allisonpollard.com
  • Providing a Safe Place for Sharing HELPFUL: Retrospective Prime Directive Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand. --Norm Kerth NOT HELPFUL: Star Trek Prime Directive No identification of self or mission. No interference with the social development of said planet. No references to space or the fact that there are other worlds or civilizations. Image by James Vaughn www.allisonpollard.com
  • 2. Gather Data Created a shared pool of data Consider objective and subjective experience Value all perspectives Photo by David Laing Use different kinds of data to get the team thinking differently! www.allisonpollard.com
  • A Variation of What Worked/What Didnt Work Photo by Wayne D. Grant Let team members organize ideas and speak to their meaning. Ask open-ended questions to increase shared understanding. www.allisonpollard.com
  • 3. Generate Insights Understand systemic influences and root causes Observe patterns See system effects Photo by Jessica Austin Move beyond habitual thinking and solving symptoms! www.allisonpollard.com
  • Based on the data, what are the trends? You can only resolve a problem if you first recognize it. Photo by Matthew Badgley www.allisonpollard.com
  • 4. Decide What to Do Move from discussion to action Resolve on actions or experiments What does the team have the energy to try in the next sprint? Photo from funretrospectives.com www.allisonpollard.com
  • Focus on what the team can do Photo by FutureWorks Consulting www.allisonpollard.com
  • What is the outcome of a retrospective? Change in Definition of Done Photo by Rachel Davies www.allisonpollard.com
  • Change in Working Agreements Photo by Ctia Oliveira www.allisonpollard.com
  • List of Action Items Photo by Jean Claude Grosjean www.allisonpollard.com
  • 5. Close the Retrospective Reiterate actions and follow-up Appreciate contributors Identify ways to make the next retrospective better Remember to thank team members for their time. Photo by Karen Greaves www.allisonpollard.com
  • Photo by FutureWorks Consulting How did the team feel about the last sprint? How do they feel about the upcoming sprint? www.allisonpollard.com
  • What should the facilitator do? Read the room Swing the pendulum Make sure everyone contributes Make sure a plan is created Dont solve the teams problems www.allisonpollard.com
  • What is the Scrum Masters role? Reflect the teams behavior back to them so they can reason out how to improve Help team members hold themselves accountable to their commitments www.allisonpollard.com
  • What should team members do? Focus on the content of the retrospective Discuss openly, which means sometimes disagreeing with others (though not disagreeably) Make decisions www.allisonpollard.com
  • References http://www.scrumshortcuts.com/blog/retrospectives- reviews/sprint-retrospective-irrespective/ http://www.estherderby.com/ http://www.coachingagileteams.com/2012/02/23/agile/most- things-work-until-they-dont http://www.innovationgames.com Agile Retrospectives: Making Good Teams Great by Esther Derby and Diana Larsen www.allisonpollard.com
  • Contact Email: allison@allisonpollard.com Twitter: @allison_pollard Blog: www.allisonpollard.com www.allisonpollard.com