agile3
Engineering Practices

Mob Programming

The whole team works on the same thing, at the same time, at one computer.

2 min read · Practitioner

In 30 seconds

  • One driver types; everyone else navigates.
  • Roles rotate every few minutes.
  • Knowledge spreads fast and handoffs disappear.

How it works

The team gathers around one screen. The driver types only what the navigators decide; the driver role rotates every few minutes. Woody Zuill and his team at Hunter Industries popularized the practice in the early 2010s. It's also called ensemble programming.

Benefits

  • No waiting on handoffs or reviews
  • Knowledge spreads across the whole team
  • Hard problems get many minds at once
  • Fewer defects reach review or testing

When to use it

  • Complex or high-risk changes
  • Onboarding new team members
  • Learning a new technology together

Many teams mob part-time and pair or work solo otherwise.

Myth vs reality

Myth · Mobbing wastes people's time.
Reality · It removes waiting and rework, which often balances out.
Myth · The loudest person runs the mob.
Reality · Rotation and facilitation keep it balanced.
Myth · Mobbing only works in person.
Reality · Remote mobs with screen sharing work well.

The AI angle

Mobbing pairs well with AI: the group can direct an AI assistant together, discuss its suggestions, and catch mistakes faster than one person would.

AI Pair Programming →

FAQ

How big should a mob be?

Often three to six people.

How often should roles rotate?

Commonly every few minutes, using a timer.

Do we mob all day?

Teams vary; take regular breaks.