Mixing without merging: comb shaping for developers, testers
summary
Argument: move from strict specialist or Swiss‑army roles to comb-shaping — multiple shallow skills with a few deep teeth — by teaching developers exploratory testing and testers to use developer tools, running pairing/ensembling sessions, and using an expectation matrix to map who owns which activities. Concrete experiments: delete the "to test" column and enforce WIP limits to force collaboration; removing core hours for six months shows no productivity drop and higher happiness. Results: lower bus factor, more empathy, incremental skill growth.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 1:51Testing evolution
- 8:11From silos to teams
- 14:33Comb shaping examples
- 18:28What is comb shaping
- 21:59Future of comb shaping
- 26:14Part-time specialists
- 30:30Individual comb shaping
- 32:18Team comb shaping exercises
- 37:17Pairing and ensembling
- 39:02Encouraging experimentation
- 40:47Managerial support
- 45:35Q&A: Resistance
- 48:46Q&A: Motivation
- 50:54Q&A: Hiring and leadership
- 52:39Q&A: Leadership vs testing
- 54:23Q&A: Remote collaboration
- 55:28Q&A: Speed impact
- 57:15Q&A: Time management
- 59:26Q&A: Convincing management
related talks
58mStepping Outside
41mMartijn Goossens: Be a Better Test Friend to Your Team
01h 06mTeaching New Tricks – How to enhance the skills of experienced developers
58mHow I became a tester!
51mDon't Put Me in a Box.
38mCompassionate Refactoring
20mWorking with Others and Delivering as a Team — Bridges Seen Through Human Relationships
33mHow to Enhance the Skills of Experienced Developers