Gang up on difficult problems with Mob Programming
summary
A team of about five to six people shares one keyboard, swaps control on a five-minute timer, and mobbed for roughly two weeks to perform a behavior-preserving refactor of large God classes that previous individual and pair attempts failed to finish. The experiment breaks the big file into smaller pieces, produces working code, creates a shared style agreement, increases follow-on refactoring PRs, requires at least three people to avoid drift, and makes remote participation and preventing a dominant driver the main practical challenges.
AI-written summary · about
chapters (5)
related talks
31mMob Programming: Team-Building Included
26mMob Programming
50mMob Programming, A Whole Team Approach
48mMob Programming: A whole team approach
01h 21mSoftware Development - Mob Programming, Pair Programming or Fly Solo?
12mTackling team dysfunctions with Mob programming -
01h 04mAdvanced Software Teaming
01h 00mMob Programming, A Whole Team Approach