Accelerated learning with Mob Programming
summary
A process for teaching junior teams through repeated mob sessions: weekly and occasional full-day runs with 4-minute rotations where the driver types but stays silent, hourly blocks of 50 minutes coding + 10-minute retros, enforced no-screen breaks and an aim to finish a story in a day, Atlassian for retro tracking and three whiteboards for evolving work. Result: rapid skill gain (teams learn in a day what used to take months), visible tooling and process bottlenecks, demos to PO and production-ready increments.
AI-written summary · about
chapters (13)
- 0:00Mob programming experiments
- 2:20What is mob programming
- 4:46First setup with juniors
- 7:18Rotation and breaks
- 9:09Hourly blocks and retrospectives
- 12:01Retrospective techniques
- 14:57Pressure cooker effect
- 17:06Second team experiment
- 20:39Overcoming resistance
- 22:45Learning mode adaptations
- 25:34Coaching gut feeling
- 26:16Retrospective guide board
- 28:25Weekly mobbing commitment
related talks
37mLearning technical practices using mob programming
12mTackling team dysfunctions with Mob programming -
31mMob Programming: Team-Building Included
01h 00mMob Programming, A Whole Team Approach
53mHalf a decade of mob programming
01h 04mAdvanced Software Teaming
54mMob Mentality Collaborative Coding and Problem Solving
01h 21mSoftware Development - Mob Programming, Pair Programming or Fly Solo?