I Don't Need Another Scrum Master, Get Me a Technical Coach!
summary
Claim: replacing another scrum master with a technical coach accelerates team ability to manage code complexity by teaching hands‑on practices. Uses Samman Method with short video‑assisted learning hours, GitHub code katas/refactoring exercises, the Hartman skill‑acquisition model and live Ensemble (mob programming) sessions to move people from comprehension to conscious action. Built a library of monthly videos, exercises and a coaching society; reports show teams adopt TDD and refactoring in production, ensembles are transformative and improvements persist after the coach leaves.
AI-written summary · about
chapters (12)
- 0:00Intro
- 0:40Modern software development is complex
- 3:10Collaborative software design
- 4:38Feedback from the real world
- 8:35Technical leadership & skill
- 11:00Test-driven development
- 13:37Skill acquisition model
- 22:49Samman Method
- 28:11Tech coach vs tech lead
- 35:01Getting beyond Code Katas
- 39:27Summary
- 41:26Outro
related talks
46mTechnical Coaching with the Samman method
29mTechnical Coaching with the Samman method
14mThe Tech Coach strikes back
42mConfessions of a Reformed Agile Coach
47mMy unusual toolbox as a scrum master and Agile coach
23mTech leadership for everyone
22mDo We Need Software Craftsmen?
01h 04mCoder, Coach, Catalyst - using questions to make people grow