Mob Programming, A Whole Team Approach
summary
Whole team works on one computer with a rotating driver/navigator rotation (typically 7–10 minutes, experimented down to 2–4) and dual big displays, a daily hour of shared study, and short end-of-day retros (≈10 minutes). Teams of 5–6 at Hunter deliver to production daily (often 2–3 times), sustain near-zero technical debt, and record only one production bug across four years; product owners commit to ~2-minute Q-time for blocking questions. Sessions use timers, shared tests, frequent refactoring, and embedded testers.
AI-written summary · about
chapters (32)
- 0:00Introduction
- 1:20Sharing Ideas
- 2:09Mob Programming
- 2:50Looking From The Front
- 3:55Starting At Lunch
- 7:06We Discovered It
- 7:55The People Do The Work
- 8:44Study Together
- 9:22Coding Dojo
- 10:14Retrospectives
- 11:19Kent Beck
- 16:17Why would we work this way
- 19:47What about the crowd
- 20:46Postit notes
- 21:06Kindness consideration respect
- 22:52How we work
- 23:24Train of thought
- 29:55How can we be productive
- 31:44Pursuing profound questions
- 32:14What destroy productivity
- 34:26Communication problems
- 36:38Faded problems
- 41:10Question queue time
- 41:54Value stream map
- 42:26Waiting time
- 46:54Technical Debt
- 47:24Quality
- 48:07Learning Attitude
- 48:51One Warning
- 49:31Ideal Team
- 49:58Getting Good
- 50:08Turn Up The Good
related talks
01h 00mMob Programming, A Whole Team Approach
46mMob Programming: A Whole Team Approach
26mMob Programming
39mMob Programming and the Power of Flow
14mGang up on difficult problems with Mob Programming
01h 24mMob programming
01h 21mSoftware Development - Mob Programming, Pair Programming or Fly Solo?
01h 04mAdvanced Software Teaming