← Back to blog

Mob Programming: When the Whole Team Codes Together

mob-programming collaboration xp

If Pair Programming is 2 people on 1 machine, Mob Programming is the entire team (4-8 people) on 1 machine. It seems inefficient — it may be the most powerful collaboration technique there is.

How It Works

Roles in the Mob

  • Driver: The person typing. Doesn’t decide, only executes.
  • Navigators: The rest of the team. They decide what and how to do it.

Rotation

Every 10-15 minutes, the driver rotates to the next person. This way:

  • Everyone goes through all positions
  • Knowledge is shared naturally
  • Nobody stays passive for too long

When Mob Programming Is Worth It

Ideal Scenarios

  • Complex problems — important architectural decisions
  • Mass onboarding — 3+ new team members
  • Solving critical bugs — all knowledge concentrated
  • Code kata — deliberate practice of techniques
  • Defining standards — when the whole team needs to align

When NOT to Use It

  • Simple features — overkill for basic CRUD
  • Tight deadlines — throughput is lower than parallel work
  • Geographically dispersed team — hard to coordinate
  • Lack of maturity — members who don’t contribute can block the mob

Estimating for Mob Programming

Throughput

Research shows that a mob of 4-6 people produces approximately:

  • 2x-3x the output of 1 person (not 4-6x)
  • But with significantly higher quality
  • Zero handoff (no need to explain it to anyone afterward)

In Planning Practice

“This task is complex and affects multiple modules. Let’s estimate as a Mob: 8 points, with the whole team, takes ~1 day.”

Vs. solo: “1 dev, 8 points = ~2 days + code review + potential bugs.”

Capacity Planning

When the team does mob work:

  • The entire team is allocated to that task
  • Other tasks are on hold
  • Plan half-day mobs to avoid fatigue

Signs of an Effective Mob

  • Everyone actively participates in decisions
  • The driver changes frequently
  • Discussions are focused on the problem
  • Juniors and seniors contribute equally
  • The result is better than it would be individually

Signs of an Ineffective Mob

  • 1-2 people dominate the conversation
  • Others are on their phones or silent
  • Sessions go beyond 2 hours
  • The result is mediocre
  • The team prefers to work alone

Tools for Remote Mob Programming

  • Tuple — remote pair/mob programming
  • VS Code Live Share — IDE sharing
  • Zoom/Meet + screen share — simple but works
  • Tuple + Miro — code + diagrams simultaneously

Conclusion

Mob Programming is the fastest way to share knowledge and make collective technical decisions. It’s not for everyday use — but 1-2 mob sessions per sprint can save days of individual work and weeks of learning.