Keynote: Technical Agile Coaching With the Samman Method
summary
A coaching method named Samman claims measurable team changes: more unit tests, more frequent commits, safer refactoring and greater TDD uptake after paired learning hours plus daily ensemble working sessions (mob programming with rotating typist/navigator roles). Demos use Cyber‑Dojo and the Mars Rover kata with ApprovalTests; Mentimeter surveys showed refactoring votes twice as high as daily integration and only ~2/10 teams had technical coaches. Typical engagement is 10 half‑day blocks, works remote or onsite.
AI-written summary · about
chapters (15)
- 0:00Samman Coaching Outcomes
- 6:07Do you see a need in your team/org to get better at any of these technical practices?
- 9:51Empowered Teams
- 12:25Test-Driven Development
- 19:09Feedback loops
- 21:53Trunk-Based Development
- 23:05Continuous Integration & Trunk based dev & TDD
- 29:31A Coding Dojo
- 33:45Learning hours have a "4C" structure
- 35:09Sample Learning Hour Outline
- 38:40Ensemble Working
- 40:12Ensemble Roles
- 51:58Mentoring
- 53:31Professional Coaching
- 57:40Team Chartering
related talks
38mTechnical Coaching
56mTechnical Coaching with the Samman method
29mTechnical Coaching with the Samman method
48mCoaching Models for Technical Agile Coaching
14mThe Tech Coach strikes back
01h 35mSoftware Teaming [Mob Programming] mini-workshop
42mConfessions of a Reformed Agile Coach
18mAgile leadership and technical mastery, a harmonious alliance