Lessons and Expierience from 15 years of Agile Coaching
summary
Fifteen years of coaching condense into concrete moves: introduce build lights and daily status emails to restore trust on an $8 million project and still deliver before SARS collapses travel; use pair programming to surface conflicts, then require a pull the cord stop‑the‑line discussion to cut escalations; run constrained experiments—two‑week safe‑to‑fail trials—rather than enforcing being right; prioritize growing influence through visible successes, expect serendipity with roughly two‑year leads from contact to engagement.
AI-written summary · about
chapters (12)
- 0:00Lessons and Experiences from 15 years of Agile Coaching
- 0:50My background might surprise you
- 2:35Anyone can learn to be a coach
- 3:03Career = Reputation + Serendipity
- 6:47Active Allocation of Influence
- 11:01Transparency = Trust = Influence
- 17:18Constrained experiments can reduce change cost
- 19:16Influence Can Be Grown (and shrunk)
- 19:53"Would you rather be right, or would you rather get things done?"
- 22:59"People over process" = process for the existing people
- 24:19Conflict is Normal (normalise resolving it)
- 26:21Technology Changes Fast, Humanity is Constant
related talks
42mConfessions of a Reformed Agile Coach
01h 01mLessons from a lifetime of doing, teaching, managing, and leading technical development
01h 03mLearning from mistakes
26mGet agile and don't die trying
01h 13mScrum for Executives, Leaders, and Your Boss
22mThe Courage to Continue and Cultural Intelligence — Insights from Agile Practice i...
28mLessons learned after more than 20 years working in IT
24m5 Lessons Learned During Agile Transformations