• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Xpde keynote
 

Xpde keynote

on

  • 708 views

 

Statistics

Views

Total Views
708
Views on SlideShare
708
Embed Views
0

Actions

Likes
0
Downloads
15
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

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.

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

    Xpde keynote Xpde keynote Document Transcript

    • Resolving Resistance to ChangeRachel Davies A bit about me• Software developer• Agile since 2000• CSM in 2003• Author of “Agile Coaching”• Conference organizer Agile Coaches Gathering, XP2011, etc 1
    • Agile Coachhelps teams grow strong in Agile practice A coach supports team rather than setting direction Agile Coach 2
    • Coaching is about Change To improve we must change! Change Across TeamsIndividuals Organization 3
    • Expect Resistance to Change Satir Change CurveWhy do people resist Change? This team is using old tools How can you influence them to change? 4
    • No time to improve!Demonstrate Another Way? 5
    • Author: J. Richard Hackman Many books about Coaching are about coaching individuals. Hackman’s book covers coaching teams. Hackman ExplainsThree kinds of coaching intervention: • Motivational - improves effort by minimizing free riding and building shared commitment • Consultative - improves process by reducing thoughtless habits and fostering invention based on situation • Educational - improves knowledge and skill You can combine these! 6
    • Consider Resistance as a Resource Article: Dale Emeryhttp://dhemery.com/articles/resistance_as_a_resource/ Dig Deeper 7
    • Listening Listening Why must a coach listen?• Show respect• Gather data• Learn feelings/opinions• Encourage• …? 8
    • Big Picture FocusStep up to see big picture Force Field AnalysisDesired change from current state 9
    • Force Field Analysis Remove barriers and amplify forces for change Prepare the GroundCreate anenvironment forthe team to growtheir own agilepractice. 10
    • What do we really want?Being Agile is not usually the real goal Share the Vision 11
    • Identify concerns Make blockers visible Visible Feedback• Help the team make information concerning their work more visible – Passing tests – User satisfaction – Value delivered – Work-in-progress limits 12
    • Reduce Work-In-Progress Limits Example of Kanban board (at BBCW) Be an Example Show how 13
    • Ask for HelpEncourage experiments Try it out 14
    • Encourage IdeasAsk the team how they would solve the problemsConsider more than one solution! 29 Go with the energy of the team What do the team want to try? 15
    • Working AgreementsStart the project with a workshop to agree how the team wants to work together.• Make agreements• Keep them• Review when they are broken Build Trust T = (C + R + I ) / S Where: T = Trust C = Credibility R = Reliability I = Intimacy S = Self-orientation Book: “The Trusted Advisor” by Maister, Green, & Galford 16
    • Be Patient Change takes time Further Reading• “Agile Coaching” by Rachel Davies & Liz Sedley• “Resistance as a Resource” by Dale Emery http://dhemery.com/articles/resistance_as_a_resource/• Virginia Satir talks about Status Quo http://web.me.com/sbuckbee1/Satirs_Process_of_Change/Status_Quo.html• “Succeeding with Agile” by Mike Cohn• “The Trusted Advisor” by David Maister• “Managing Transitions” by William Bridges• “Fearless Change” by Linda Rising and Mary Lynn Manns• “Leading Teams” by Richard Hackman 17
    • Contact MeEmail: rachel@agilexp.comTwitter: rachelcdaviesBlog: http://agilecoach.typepad.com/ 18