The Tech Coach strikes back
summary
Companies spend heavily on agile coaches but neglect technical coaching; remedy is regular mob programming sessions with a big screen, driver/navigator roles and a facilitator. Start with rotate every 4 minutes so everyone is driver and navigator at least once, meet 1–2 hours weekly, work on real production bugs or a 2,000‑line class, practice TDD, CI and continuous refactoring. Result: fewer maintenance nightmares, faster onboarding, happier developers and measurable drops in tech debt.
AI-written summary · about
chapters (12)
- 0:00Intro
- 1:57How is support
- 3:08Does coaching help
- 4:13What is technical coaching
- 5:26What doesnt happen
- 6:47Mob Programming
- 10:01Use XP
- 10:26Adjust solutions
- 11:02Have fun
- 11:40Next time
- 11:53Final tip
- 12:20Summary
related talks
37mLearning technical practices using mob programming
48mCoaching Models for Technical Agile Coaching
46mTechnical Coaching with the Samman method
56mTechnical Coaching with the Samman method
12mTackling team dysfunctions with Mob programming -
01h 15mKeynote: Technical Agile Coaching With the Samman Method
42mI Don't Need Another Scrum Master, Get Me a Technical Coach!
23mTech leadership for everyone