Practice : Mob Programming

Purpose and Strategic Importance

Mob Programming is a practice where the whole team works together on the same task, at the same time, in the same space (or virtual space). It extends the benefits of pair programming - shared understanding, early feedback, and high quality - to the full team level.

Mob programming helps eliminate silos, improves team communication, accelerates knowledge transfer, and strengthens team culture. It's particularly valuable for complex problem solving, onboarding, cross-functional alignment, and continuous improvement.

Description of the Practice

  • One person types (the driver), while the rest of the team (navigators) actively guide, review, and discuss.
  • Roles rotate at regular intervals (e.g. every 5–15 minutes).
  • Common tools include collaborative IDEs, shared terminals, and video conferencing platforms.
  • Works best when the task is collaborative in nature - new features, design spikes, infrastructure changes, or tricky bugs.
  • Can be adopted ad-hoc or as a regular part of the team’s workflow.

How to Practise It (Playbook)

1. Getting Started

  • Choose a problem worth solving collaboratively - one that benefits from diverse perspectives.
  • Set up a timer to rotate roles regularly and keep energy levels high.
  • Designate a facilitator to manage flow, participation, and psychological safety.
  • Debrief after each session to reflect on what’s working and what could be improved.

2. Scaling and Maturing

  • Mob regularly for complex, high-impact, or learning-heavy work.
  • Use mobbing as a levelling-up tool for new joiners or emerging leaders.
  • Incorporate product, design, and QA into mobs to drive alignment and shared ownership.
  • Share techniques like strong-style navigation or silent thinking rounds.
  • Create inclusive norms: everyone contributes, all voices are valued.

3. Team Behaviours to Encourage

  • Focus on collaboration over competition - mobbing is about team flow, not individual speed.
  • Embrace diverse thinking styles - make space for quiet reflection and active discussion.
  • Encourage empathy, patience, and curiosity.
  • Celebrate mobbing as both a delivery and learning practice.

4. Watch Out For…

  • Long sessions without breaks leading to fatigue.
  • Dominant voices or uneven participation.
  • Skipping retrospectives and reflection time.
  • Assuming every task requires a mob - use the right tool for the right context.

5. Signals of Success

  • Teams deliver higher-quality outcomes with fewer handoffs.
  • Onboarding and learning curves shrink dramatically.
  • Cross-functional understanding deepens.
  • Morale, psychological safety, and shared ownership increase.
  • Complex problems get solved more effectively with collective input.