Software Teaming (Mob Programming) and the Power of Flow.
summary
Claims that five people at one computer produce 10× throughput and only 3 production bugs in 3.5 years come with concrete practices: one person drives at the keyboard while the rest guide, rotate roles, and keep product owners testers DB and deployment people as part of the team to eliminate waiting. Teams measure blocking question wait time with simple value‑stream maps, aim for one‑piece flow, and combine individual psychological flow with collective team flow so answers arrive immediately and inventory, context switches, and rework decrease.
AI-written summary · about
chapters (11)
- 0:00Introduction and background
- 9:02What is mob programming?
- 14:01Benefits of software teaming
- 22:01Productivity vs effectiveness
- 31:27Questioning solo work assumptions
- 33:56Communication problems and waste
- 39:54Psychological flow and teamwork
- 45:16Lean flow in software
- 51:19Optimizing for flow over output
- 56:17Creating environments for greatness
- 57:54Q&A on influencing change
related talks
39mMob Programming and the Power of Flow
01h 04mAdvanced Software Teaming
42mAdvanced Software Teaming [Mob Programming]
45mAdvanced Software Teaming
01h 00mMob Programming, A Whole Team Approach
01h 35mSoftware Teaming [Mob Programming] mini-workshop
01h 21mSoftware Development - Mob Programming, Pair Programming or Fly Solo?
50mMob Programming, A Whole Team Approach