Mob Programming and the Power of Flow
summary
Five-plus people share one workstation and route every change through a single keyboard while navigators propose ideas and a driver types, producing one-piece flow and daily deployments. Teams report far fewer defects — three bugs in 3.5 years at origin — and faster cycle time by collapsing queue time and inventory. Team psychological flow and lean flow combine to speed decision-making; one effort even gathers 14 people session to finish a single critical feature.
AI-written summary · about
chapters (12)
- 0:00Start
- 15:13Working Separately
- 19:38A short list of things that can destroy effectiveness
- 22:38Question Queue Time
- 26:10How do we typically solve this?
- 28:32Flow vs. Flow
- 30:55Is there a "team" psychological Flow, and what is that like?
- 33:05We Enable Team FLOW by Working Well Together
- 34:48The Principle of Queueing Waste
- 35:20Queues create
- 35:42Flow with Software Development
- 38:02Flow Plus Flow
related talks
01h 05mSoftware Teaming (Mob Programming) and the Power of Flow.
01h 00mMob Programming, A Whole Team Approach
26mMob Programming
46mMob Programming: A Whole Team Approach
50mMob Programming, A Whole Team Approach
44mMob Programming: Learn Together. Deliver Together
31mMob Programming: Team-Building Included
01h 04mAdvanced Software Teaming