Migrating from Pair to Mob Programming

Many teams evolve from pairing to occasional mobs, then to regular mob sessions for complex work. A smooth transition reduces friction and skepticism.

Why Transition?

• Accelerate architectural alignment.
• Reduce knowledge silos.
• Increase onboarding velocity.

Phased Approach

1. Experiment: Run a single 60‑minute mob on a well-scoped feature.
2. Reflect: Capture benefits & pain points; adjust rotation length.
3. Targeted Use: Schedule mobs for high-complexity stories and production issues.
4. Integration: Combine with pair execution after mob alignment.
5. Normalization: Add a lightweight ritual (daily 30–60 min alignment mob).

Addressing Concerns

• "Too many people on one task" → Emphasize reduced rework & decision latency.
• "Slow typing" → Focus on thinking quality, not keystrokes.
• "Some stay quiet" → Use facilitation prompts & rotate roles.

Metrics to Watch

• Lead time for complex changes.
• Defects found post-merge.
• Onboarding time to first meaningful commit.
• Cross-team bus factor (number of people comfortable with module X).

Toolkit

• Timer (this app)
• Lightweight shared note doc
• Parking lot list for deferred topics

Transition intentionally, measure impact, and adapt. The goal isn't more mobbing—it's better collaboration outcomes.