1 Resolving Resistance to Change Rachel 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
Resolving Resistanceto Change
Rachel Davies
A bit about me
• Software developer
• Agile since 2000
• CSM in 2003
• Author of “Agile Coaching”
• Conference organizerAgile Coaches Gathering,XP2011, etc
2
Agile Coach
helps teams grow strong in Agile practice
A coach supports teamrather than setting direction
Agile Coach
3
Coaching is about Change
To improve we must change!
Change Across
Individuals
Teams
Organization
4
Expect Resistance to Change
Satir Change Curve
Why do people resist Change?
This team is using old tools
How can you influence them to change?
5
No time to improve!
Demonstrate Another Way?
6
Author: J. Richard Hackman
Many books aboutCoaching are aboutcoaching individuals.Hackman’s book coverscoaching teams.
Hackman ExplainsThree kinds of coaching intervention:
• Motivational - improves effort by minimizingfree riding and building shared commitment
• Consultative - improves process by reducingthoughtless habits and fostering invention basedon situation
• Educational - improves knowledge and skillYou can combine these!
7
Consider Resistance as aResource
Article: Dale Emeryhttp://dhemery.com/articles/resistance_as_a_resource/
Dig Deeper
8
Listening
Listening
Why must a coach listen?
• Show respect• Gather data• Learn feelings/opinions• Encourage• …?
9
Big Picture Focus
Step up to see big picture
Force Field Analysis
Desired change from current state
10
Force Field Analysis
Remove barriers and amplify forces for change
Prepare the Ground
Create anenvironment forthe team to growtheir own agilepractice.
11
What do we really want?
Being Agile is not usually the real goal
Share the Vision
12
Identify concerns
Make blockers visible
Visible Feedback
• Help the team makeinformation concerningtheir work more visible– Passing tests– User satisfaction– Value delivered– Work-in-progress limits
13
Reduce Work-In-Progress Limits
Example of Kanban board (at BBCW)
Be an Example
Show how
14
Ask for Help
Encourage experiments
Try it out
15
29
Encourage Ideas
Ask the team howthey would solvethe problems
Consider more thanone solution!
Go with the energy of the team
What do the team want to try?
16
Working Agreements
Start the project with a workshop to agree howthe team wants to work together.
• Make agreements
• Keep them
• Review when they are broken
Build Trust
T = (C + R + I ) / SWhere:
T = Trust
C = Credibility
R = Reliability
I = Intimacy
S = Self-orientationBook: “The Trusted Advisor” by Maister, Green, & Galford
17
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 Quohttp://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