Mob Programming, A Whole Team Approach
summary
Whole team sits at one computer with a timed driver/navigator rotation (about every 15 minutes), product owners nearby, and a practice of 10-minute daily retrospectives plus weekly three‑hour study dojos. Result: story cycle time drops from weeks to hours, merging conflicts disappear, onboarding becomes immediate, and question‑queue time collapses so teams deploy 2–3 times per day. Teams size and skill mix target whoever prevents blocking; focus is on communication, real‑time review, and sustaining a relaxed, sustainable pace.
AI-written summary · about
chapters (14)
- 0:00Start
- 13:03Driver/Navigator
- 23:32Let's figure out how to work well together
- 24:09Weekly Team Study And Practice Session
- 25:11Using a Coding Dojo style of deliberate practice
- 32:58Why would we work this way?
- 36:59How can we work this way?
- 42:01Relaxed, Sustainable
- 47:06What are the things that destroy productivity?
- 54:51Question Queue Time
- 55:20How do we typically solve this?
- 56:38How did we Solve This?
- 57:51What is the Ideal Number of Team Members?
- 59:16Mob Programming Book
related talks
50mMob Programming, A Whole Team Approach
46mMob Programming: A Whole Team Approach
39mMob Programming and the Power of Flow
26mMob Programming
01h 04mAdvanced Software Teaming
29mAccelerated learning with Mob Programming
31mMob Programming: Team-Building Included
01h 05mSoftware Teaming (Mob Programming) and the Power of Flow.