Advanced Software Teaming [Mob Programming]
summary
Advocates a concrete shift: put the whole team at one computer using driver navigator rotations and the rule that any code idea must pass through someone else’s hands. Teams run as a protected “bubble” so the org can’t interrupt experiments, and turning collaboration up — turn up the good — collapses a previously recurring 50-item problem list; many blockers fade, communication becomes continuous alignment, and small habit improvements compound over months. Calls it mob programming / Software Teaming and notes it works remotely.
AI-written summary · about
chapters (20)
- 0:00Advanced teaming intro
- 3:40What is mob programming
- 6:09Philosophy behind teaming
- 8:12Tiny improvements growth
- 10:16Why problems persist
- 13:25Cycle of no improvements
- 15:32Problem-solving focus flaw
- 17:19Beliefs biases reality
- 20:09Success luck pride
- 22:56Wheeler’s Law failure
- 25:48Systems thinking problems
- 28:13Understanding domains
- 30:21Theory to techniques
- 31:02Turning Up the Good in Collaboration
- 35:17Work smarter not harder
- 36:20Make work easy
- 37:04Bubble concept change
- 38:29Collaboration over communication
- 39:33Leading from within
- 40:56Closing Q&A
related talks
01h 04mAdvanced Software Teaming
45mAdvanced Software Teaming
31mMob Programming: Team-Building Included
01h 05mSoftware Teaming (Mob Programming) and the Power of Flow.
48mMob Programming: A whole team approach
26mMob Programming
46mMob Programming, the True Approach to Team Development
12mMOB Programming as Equilibrium