Keynote
summary
Claims that colocated teams at one keyboard produce far more useful, higher-quality work: experiments report roughly ten times the finished work and only three bugs in 3.5 years after adopting the practice. Uses a strict driver-navigator rotation (originally 15 minutes), daily learning sessions, and product owners who commit to fast answers — creating effectively zero question queue time. Outcome: one-piece flow, much less multitasking and inventory, and simultaneous individual and team flow.
AI-written summary · about
chapters (16)
- 0:00Start
- 1:52Monkey Puzzle Tree
- 4:36Introduction to Mob Programming Mob Programming
- 5:18Agile Manifesto
- 6:59Driver Navigator
- 10:44Pre Mob Programming
- 14:54A System Is Not the Sum of the Behavior of Its Parts It's the Product of Their Interactions
- 15:17Efficiency Productivity and Effectiveness
- 17:50How Can We Be Productive
- 19:32What Are the Things That Destroy Effectiveness
- 20:50Communication Problems
- 21:12The Question Queue Time
- 25:18Losing the Sense of Time
- 31:09Flowing Lean
- 32:13Value Stream Map
- 40:13Team Flow
related talks
39mKeynote - The gordian knot
48mWe're Good At Writing Software [Keynote]
15mKeynote: The Self Driving Company
58mKeynote: Seven Habits of a (Mostly) Successful Team
43mKeynote: Coding Culture
01h 05mSoftware Teaming (Mob Programming) and the Power of Flow.
50mMob Programming, A Whole Team Approach
53mKeynote: Managing for Happiness