Confessions of a Reformed Agile Coach
summary
Becomes a programmer on a team maintaining 15–20 year legacy code and discovers standard coaching rituals actually distract from deep work; replaces rote stand-ups with paired work on the same story, tracks frustrations on sticky-note issues during the week, runs off-site retrospectives and embeds coaching on the team. Claims permanent coaching teams are a smell unless leadership first accepts coaching; the concrete changes increase rapport, surface real technical blockers, lengthen useful discussion, and improve delivery of fixes.
AI-written summary · about
chapters (11)
- 0:00John Wooden's coaching legacy
- 2:45Rise of agile coaching
- 5:03From coach to team realities
- 8:41Dog fooding as reformed coach
- 16:41Coaching fails without leadership
- 24:45Agile future needs leadership
- 27:13Fixing hated agile ceremonies
- 33:57Permanent coaching teams unsustainable
- 36:54Generational gap in agile
- 38:51Understanding team challenges
- 40:57Q&A
related talks
28mLessons and Expierience from 15 years of Agile Coaching
48mCoaching Models for Technical Agile Coaching
38mScaling Continuous Improvement mindset and making it stick
24mWhy I Stopped Coaching Agility and So Should You!
47mCodeCraft Leadership: Hacking the DNA of Agile Teams
01h 15mKeynote: Technical Agile Coaching With the Samman Method
36mA Life Discovering Agile
01h 04mCoder, Coach, Catalyst - using questions to make people grow