Technical Coaching with the Samman method
summary
Describes a concrete coaching recipe that spreads TDD and refactoring by running repeated Learning Hour exercises (code katas like Gilded Rose, approval testing, 4C active-learning) plus supervised Ensemble working sessions with explicit roles (typist, navigator, supporters). Typical engagement is 10 half days per team, remote or in-person; reported effects are more tests, more refactoring, more frequent commits and better collaboration. Cites research that developers lose about 23% of time to technical debt and shows this method reduces that.
AI-written summary · about
chapters (22)
- 0:00Intro
- 0:46What situations make coding fun?
- 9:47Code Quality & Technical Debt
- 10:36Keep Technical debt under control
- 11:06Skill, Technical Excellence
- 12:08Test-Driven Development
- 13:13Accelerate research
- 14:16Manage tech debt - skills
- 15:16browbeating
- 16:02A new way of skiing
- 16:46Coding Dojos
- 22:05Samman Coaching Outcomes
- 24:08Training from the back of the room
- 25:10Learning Hours
- 26:15In your normal coding work, how much time do you spend...
- 27:53Ensemble Working
- 29:38Ensemble Roles
- 32:22Onboarding workshops
- 32:52Blocks of 10 half days
- 38:52Story - Career choices
- 41:39Lowering the barrier to entry
- 43:31Creating a community
related talks
01h 15mKeynote: Technical Agile Coaching With the Samman Method
14mThe Tech Coach strikes back
48mCoaching Models for Technical Agile Coaching
23mTech leadership for everyone
25mConvert your team into TDD enthusiasts
26mTest Coaching
40mClosing Keynote
06mA Simple Talent Development Program for Software Departments