Advanced Software Teaming
summary
Claims that whole-team Mob Programming (everyone at one computer — coding, testing, designing with the Product Owner) cuts queuing and inventory, creates continuous alignment, and yields faster shared understanding. Uses simple tools: one shared monitor, remote screen tools (TeamViewer/Zoom/remote mob sites), adapters and a protected culture bubble to experiment. In practice small trials (20 people made 50 problem notes in 3 minutes) and months of mobs make many symptoms fade, capability rises (compounding idea: 1% daily → 37.7×) and adoption spreads across teams. turn up the good
AI-written summary · about
chapters (21)
- 0:00Introduction
- 1:31Software teaming
- 4:23Team collaboration principles
- 7:14Tiny improvements power
- 9:21Obstacles in software work
- 13:15Symptoms vs underlying problems
- 15:25Management misplaced focus
- 17:10Beliefs biases reality
- 20:46Success luck talent
- 22:10Why communication fails
- 24:42Systems and complexity
- 27:13Theory to practical steps
- 27:58Working in different domains
- 32:14Turning up the good on collaboration
- 36:07Smarter vs harder work
- 39:16Flow over output
- 41:04Culture bubbles for change
- 44:39Fixing communication
- 46:46Leading change
- 51:21Summary
- 1:00:51Q&A
related talks
42mAdvanced Software Teaming [Mob Programming]
45mAdvanced Software Teaming
31mMob Programming: Team-Building Included
48mMob Programming: A whole team approach
26mMob Programming
01h 05mSoftware Teaming (Mob Programming) and the Power of Flow.
46mMob Programming, the True Approach to Team Development
12mMOB Programming as Equilibrium