10 irrefutable laws of agile coaching

Click here to load reader

download 10 irrefutable laws of agile coaching

of 14

  • date post

  • Category


  • view

  • download


Embed Size (px)


This slide was presented at the LAST(Lean Agile Systems Thinking) conference 2014 in Melbourne. Agile coaching is one of sought after skills in the IT industry and many experienced coaches are doing extremely well. However some change agents are struggling to make an impact, not because, they don't know Agile but because, they don't know some ground rules dealing with the coaching teams and leaders. Whether you are a novice or an experienced coach, there are irrefutable laws governing Agile coaches. Based on my own personal experiences coaching teams/leaders since the last several years, I have come to realize the 10 secrets. Irrespective of where you are in the journey as an Agile coach, practicing these 10 laws will help you to become a successful Agile coach. These handy rules can help you anywhere in Agile coaching journey.

Transcript of 10 irrefutable laws of agile coaching

  • 10 Irrefutable laws of Agile Coaching Venkatesh Krishnamurthy http://agileworld.blogspot.com @ venky_nk Venkatesh Krishnamurthy
  • Author, Advisor and Speaker Co-Author: Who is Agile in Australia and New Zealand https://leanpub.com/whoisagileAustralia
  • 1. Knowing Agile, Kanban and Lean wont make you an Agile coach Conflict Managemen t Planning Team Building Decision Making Empath y Persuasio n Influencing Motivational
  • 2. Be an Alien when you start with a new team http://lunatractor.com/2011/05/13/great-agile-workspaces-how-we- communicate/
  • 3. Have the ability to have two opposing ideas in mind
  • 4. Be within the system to change the system Systems are like Russian Dolls. One is nested in another. Teams are nested within a large group. The group is nested under a larger portfolio Each of the nested systems interact and impact all the time Trying to change one area without understanding the impact or the influence will be futile One cannot create a new system from scratch. New system should be built on the existing system
  • 5. Build Trust and Relationship before Stand Up and Retrospective skills Deterrence based Knowledge based Identity based
  • 6. Work directly with Stakeholder who pays money
  • 7. Dont escalate against your own team
  • 8. If you cant change the system, you will end up becoming part of the system
  • 9. You are a doctor and listen to the symptoms and prescribe the medicine
  • 10. Practices are context dependent Practices that could work for one team may not work for the others