Advanced Software Teaming
summary
Argues that Software Teaming (Mob Programming) is a practical way to remove common wastes — context switching, handoffs, unclear requirements and failing communication — by having the whole team work on one computer in one space (or a single virtual meeting). Describes experiments at Hunter Industries (2011) and remote setups, uses Cynefin sense‑making, a culture bubble to protect experiments, and the 1% per day = 37.78× tiny‑improvements habit; shows turning up collaboration knobs often makes those problems vanish.
AI-written summary · about
chapters (15)
- 0:00Introduction to teaming
- 2:22Core teaming dynamics
- 3:50The habit of improvement
- 6:12Identifying obstacles
- 8:21Symptoms vs. root causes
- 11:53The problem with problems
- 14:01Biases and beliefs
- 17:48Success, luck, and decay
- 20:28Communication failure
- 23:22Systems and evolution
- 26:33Navigating domains
- 30:58Advanced teaming strategies
- 34:23Turning up the good
- 39:05Bubbles and collaboration
- 43:24Leading from within
related talks
42mAdvanced Software Teaming [Mob Programming]
01h 04mAdvanced Software Teaming
01h 05mSoftware Teaming (Mob Programming) and the Power of Flow.
01h 35mSoftware Teaming [Mob Programming] mini-workshop
01h 21mSoftware Development - Mob Programming, Pair Programming or Fly Solo?
31mMob Programming: Team-Building Included
01h 00mMob Programming, A Whole Team Approach
50mMob Programming, A Whole Team Approach