practiceEngineering & architecture

Mob Programming

A whole-team collaboration practice in which several people work together on one problem through a single active development environment.

Download Markdown (.md)

01What it means

Mob programming, also called ensemble programming, brings a team together to perform the same development work at the same time, on the same problem, through one active computer or shared session. One person acts as driver and translates the group's current intent into code or commands; the other participants navigate. Roles rotate frequently so knowledge, influence, and hands-on participation move through the group.[1][2]

One problem, one active environment, whole-team thinking The driver executes the group's current intent while everyone continuously contributes
DriverOperates the keyboard and development environment
Implements the immediate direction; does not decide alone
NavigatorArticulates the next small step
Translates group reasoning into executable intent
MobReviews, researches, tests, and anticipates
Shares context and challenges the direction constructively
FacilitatorProtects flow and participation when needed
Supports rotation, breaks, conflict, and working agreements

Roles rotate frequently; the practice depends on psychological safety, accessible participation, breaks, and a problem worth concentrated group attention.

02Why it matters

A mob can combine development, testing, domain, design, and operational perspectives without repeated handoffs. Questions are answered while decisions are made, and knowledge spreads through direct participation. For uncertain or cross-cutting work, the resulting alignment can be more valuable than maximizing the number of tasks started simultaneously.

03When to use it

Use mob programming for difficult incidents, architectural spikes, unfamiliar systems, onboarding, or changes that require several specialties to coordinate closely. Teams may mob continuously or only for selected work. The cost is easiest to justify when delay, misunderstanding, or knowledge concentration poses more risk than concentrating several people on one item.

04How it works

  1. Choose one valuable, suitably bounded objective and invite the perspectives needed to complete it.
  2. Provide a shared screen, audio, development environment, and facilitation that work for local or remote participants.
  3. Assign one driver to execute instructions while the remaining participants navigate and discuss direction.
  4. Rotate the driver on a short, predictable cadence and make room for quieter participants.
  5. Keep the work in small testable steps, pausing when the group lacks a shared understanding.
  6. Retrospect on flow, inclusion, fatigue, and outcomes, then adjust group size and session length.

05A practical example

Example

A team must migrate authorization logic used by four services. A security specialist, domain expert, tester, and developers mob for two hours. They map rules, add characterization tests, and move one policy behind a shared interface. Frequent driver rotation exposes setup gaps and distributes knowledge that previously belonged to one maintainer.

06Where it breaks

A large group can amplify distraction, conformity, and fatigue. Dominant voices may steer the work while others disengage, even when roles rotate. Mobbing also reduces parallel work and becomes costly when the objective is unclear or participants are unnecessary. It requires facilitation, accessible tooling, and deliberate breaks rather than simply adding people to a call.

Common mistakes

  • Inviting a crowd without a clear objective or relevant reason for each perspective.
  • Letting the driver decide direction instead of implementing the navigators' shared intent.
  • Rotating the keyboard while leaving conversational influence unchanged.
  • Evaluating the practice only by individual utilization rather than completed value and learning.

07Sources

  1. What is Mob Programming?Agile Alliance · Professional practice guideWhat is Mob Programming?
  2. Mob Programming — A Whole Team ApproachAgile Alliance · Practitioner experience reportMob Programming — A Whole Team Approach
View saved topics

Start typing to search titles, definitions, categories, and frameworks.