The Changing Landscape of Collaborative Development
Mob programming—where an entire team works on the same code, at the same computer, at the same time—has proven to be a powerful practice for many development teams. But as remote work becomes increasingly common, many teams are adapting this practice to virtual environments. While the core principles remain the same, remote mob programming introduces several distinct challenges and opportunities that differentiate it from traditional on-site sessions.
Communication Dynamics
The most immediate difference between remote and on-site mob programming is the communication channel. In-person sessions benefit from natural face-to-face interaction, where participants can observe body language, easily interrupt, and use physical gestures to communicate ideas. Conversations flow naturally, and whiteboarding happens spontaneously.
Remote sessions, however, rely on video calls where subtle visual cues may be missed, audio delays can disrupt the natural flow of conversation, and only one person can typically speak effectively at a time. This changed dynamic requires more deliberate communication protocols and explicit turn-taking to ensure everyone remains engaged and heard.
Technical Handovers
On-site mob programming typically uses a single physical machine where team members physically rotate the keyboard. The environment remains consistent throughout the session, with no need to transfer code between machines.
Remote mob programming, however, requires establishing a reliable technical workflow for transferring control between drivers. This often involves git-based handovers or screen-sharing solutions, adding complexity that doesn't exist in the on-site scenario. Tools like mob.sh or custom git workflows become essential to maintain momentum during driver rotations.
I've written a guide on how I usually go about the git handover during a remote session.
Maintaining Focus and Energy
In-person mob sessions benefit from the physical presence of teammates, which naturally helps maintain focus and energy. It's immediately apparent when someone disengages, and the shared physical space creates accountability.
Remote sessions make it easier for participants to multitask or disengage without others noticing. The isolation of working from home can also lead to faster mental fatigue during intense collaborative sessions. This makes structured timing, regular breaks, and clear rotation schedules even more critical in the remote environment.
Tooling Requirements
On-site mob programming requires minimal specialized tools—often just a large monitor and comfortable seating arrangement.
Remote mob programming demands a robust technical infrastructure: reliable internet connections, quality audio/video equipment, shared development environments, screen sharing platforms, and specialized tools for timing and rotation management like Remobster.
Inclusive Participation
One advantage of remote mob programming is that it can potentially create more equitable participation. In physical settings, dominant personalities can sometimes control the room, and spatial arrangements may inadvertently create hierarchies.
In remote settings, everyone has the same size "window" in the meeting, and tools like chat functions provide alternative ways to contribute. However, this requires intentional facilitation to ensure quieter team members remain engaged and comfortable contributing.
Making Remote Mob Programming Work
Despite these differences, remote mob programming can be just as effective as its on-site counterpart when teams:
- Establish clear communication protocols
- Implement efficient handover processes
- Use dedicated tools for timing and rotation management
- Schedule regular breaks to maintain energy and focus
With thoughtful adaptation and the right supporting tools, remote mob programming can deliver the same benefits of knowledge sharing, high-quality code, and team cohesion that make on-site mob programming so valuable.