Mob Programming
summary
A team works together on a single task at one computer one keyboard one display, using the driver/navigators pattern so every idea passes through another pair of hands, with drivers rotated every 10–50 minutes (some teams enforce rotation with a timer or keyboard-locking app). Originating at Hunter Industries in 2010, mobs report outcomes like collective code ownership, faster onboarding, fewer critical defects, and even teams scaling up to 25 people.
AI-written summary · about
chapters (11)
- 0:00Start
- 9:40Collective Code Ownership
- 10:14Knowledge Transfer
- 12:48Increase Productivity
- 15:16How does it work?
- 18:54Risks and pitfalls?
- 19:17FOCUS
- 19:59Discipline
- 20:42Communication
- 21:03Maturity
- 23:25Participate or learn
related talks
46mMob Programming: A Whole Team Approach
48mMob Programming: A whole team approach
50mMob Programming, A Whole Team Approach
31mMob Programming: Team-Building Included
01h 00mMob Programming, A Whole Team Approach
39mMob Programming and the Power of Flow
01h 24mMob programming
01h 04mAdvanced Software Teaming