Tackling team dysfunctions with Mob programming -
summary
Mob programming combined with short TDD exercises produces a measurable side effect: teams gain trust, accept vulnerability, have more constructive conflict and stronger commitment. Sessions run as short blocks — often 2–3 hours per week or part of a 3‑month apprenticeship — using driver/navigator roles where the navigator protects the driver and the facilitator can temporarily take the navigator role. For large groups a fishbowl for ~15 people keeps the mob usable and focused.
AI-written summary · about
chapters (7)
- 0:00Introduction and background
- 3:01Mob programming basics
- 4:05Team dysfunctions and trust
- 6:11Mob programming effects on team dynamics
- 7:42Mob programming characteristics
- 10:07Product owner involvement
- 11:31TDD skill progression with mob
related talks
37mLearning technical practices using mob programming
31mMob Programming: Team-Building Included
29mAccelerated learning with Mob Programming
01h 04mAdvanced Software Teaming
44mMob Programming: Learn Together, Deliver Together!
46mMob Programming, the True Approach to Team Development
42mAdvanced Software Teaming [Mob Programming]
14mGang up on difficult problems with Mob Programming