Technical Coaching with the Samman method
summary
A concrete coaching method that teaches TDD and refactoring with short practice sessions and live work in a real codebase, split into a structured Learning Hour (exercise-based, active learning) and two-hour Ensemble Working sessions where the whole team collaborates on backlog tasks. Coaches work part-time with teams in blocks (typically 10 half days), use pairing and role rotation, and report outcomes: more unit tests, more frequent commits and refactoring, better collaboration; external research shows about 23% average developer time wasted on technical debt.
AI-written summary · about
chapters (9)
- 0:00Introduction to talk
- 3:19Productivity and well-being
- 10:24Technical debt problem
- 17:25Learning TDD effectively
- 22:22Introducing Samman method
- 29:03Ensemble working explained
- 33:23Coaching structure and cadence
- 37:13Why technical coaching matters
- 40:21Career path for coaches
related talks
29mTechnical Coaching with the Samman method
42mI Don't Need Another Scrum Master, Get Me a Technical Coach!
14mThe Tech Coach strikes back
23mTech leadership for everyone
30mLessons Learned: A Developer's Perspective on Teaching & Learning
33mCoaching through Coding
45mMaking Learning Conscious — How and why to build a learning culture
49mApprenticeship programs
