Software Teaming: Onboarding, Remote Work, Productivity — Four Years in an Team's Life
summary
A nine-person product and data team practiced mob programming (software teaming) for four years, working full-remote and shipping weekly demos. They use a single stack (TypeScript, Node, Redis, Postgres, React), trunk-based development with branch-by-abstraction and continuous TDD, manage interruptions via a rotating “Batman” role and split into focused mob/pair groups when needed, and use Live Share and Gather Town for remote presence to achieve faster onboarding, sustained quality, and fewer merge conflicts.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 3:12Comet team
- 7:02MOB programming setup
- 12:56Tech choices
- 16:08Psychological safety
- 21:45MOB remote
- 25:20Adaptive configs
- 30:56Junior onboarding
- 34:04Rituals learning
- 35:08Feature factory risk
- 36:13Recommended resources
- 38:18Q&A
related talks
53mHalf a decade of mob programming
42mIncredible Agile Teams
29mAccelerated learning with Mob Programming
45mFrom 5 to 100 in Product Development team in just 5 years
12mTackling team dysfunctions with Mob programming -
23mTech leadership for everyone
31mProductionalizing a Data Science Team
47mBumpy 12 Months Road to Transform Team of Mercenaries Into Product Minded Team