Half a decade of mob programming
summary
Six years of daily mob programming, two years colocated then fully remote, shows concrete gains: continuous organic knowledge sharing across the whole team, steadier code quality, and faster consensus-driven design. Practical setup: one shared team computer accessed via AnyDesk, a single team Slack identity, Miro for whiteboarding, a big mic/headsets for hybrid, and when three drivers used an 8‑minute timer to rotate. Best size is 3–5 people; juniors get a few solo hours to build confidence.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:10Speaker motivation
- 5:02What is software teaming
- 11:09Benefits of teaming
- 17:52Clearer solutions
- 21:13Quality and teamwork
- 25:07Succeeding with teaming
- 30:47Common challenges and how to overcome them
- 38:13Remote teaming
- 40:02Onboarding juniors
- 41:04Traditional vs teaming
- 47:25Why teaming should be default
- 48:28Summary
related talks
48mSoftware Teaming: Onboarding, Remote Work, Productivity — Four Years in an Team's Life
29mAccelerated learning with Mob Programming
12mTackling team dysfunctions with Mob programming -
14mThe cost of Mob Programming
44mMob Programming: Learn Together, Deliver Together!
24mtalks about joining a MOB
14mThe Tech Coach strikes back
42mIncredible Agile Teams