Promiscuous Pairing - Yes it works!!!
summary
Team adopts promiscuous pairing with frequent rotations (example: 60‑minute cycles using a 12/12/6 rotation and short Pomodoro breaks), driver/navigator roles, and strict small, independent tasks. Result: faster knowledge transfer across a six‑person feature team, removal of single‑person dependencies when one dev leaves, cleaner consistent code via continuous integration, and a claimed beginner's mind benefit that yields dramatically fewer production bugs (reported as roughly 15–20× improvement) while keeping steady output.
AI-written summary · about
chapters (5)
- 0:00Start
- 1:48Why we moved to promiscuous pairing?
- 2:55Promiscuous Pairing and Beginner's Mind: Embrace Inexperience Arlo Belshee
- 16:01team composition
- 17:59finding optimum pair switching frequency
related talks
41mLearning faster
28mThe critical aspects of our transformations DevOps, Agile, Ecological
50mGive agility back to developers!
57mContinuous Discovery: The Power of Pure Agile
41mProduct Owner & Developer: An Unexpected Journey
19mAgile Playground: The Power of Experimentation
16mSplitting the Team
16mSmall Scale Scrumming