MOB Programming as Equilibrium
summary
Argues that running a whole team together on a single computer (mob programming) produces continuous distribution of knowledge and continuous code review, which surfaces gaps and cuts defects so the team spends less time fixing and more on new value. Gives concrete examples: a team changes a button without the absent web specialist, implements a dark mode toggle together, and has a scrum master who can type code, removing QA and release silos and reducing bottlenecks to increase flow.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:40stagnant water
- 2:11thesis
- 3:18maximizing capabilities
- 3:58MOB programming
- 4:59Minimize defects
- 6:20Dont build the wrong thing
- 7:50Minimize bottlenecks
- 9:03Minimize asynchronous
- 10:23Summary
related talks
31mMob Programming: Team-Building Included
48mMob Programming: A whole team approach
46mMob Programming, the True Approach to Team Development
01h 04mAdvanced Software Teaming
04mMob Programming and NoEstimates
26mMob Programming
42mAdvanced Software Teaming [Mob Programming]
01h 21mSoftware Development - Mob Programming, Pair Programming or Fly Solo?