explore · Knowledge Sharing, Problem Solving · 60–240 min · 3-5 people · medium energy
Remote Mob Programming
A small team works on one task at the same time on one shared screen, fully remote. One person is the typist and only types what the rest of the group tells them; the others discuss and decide. The typist role rotates every ten minutes, and the work in progress is handed to the next typist so they can share their screen and carry on.
When to use Remote Mob Programming
Use when a team needs to solve a hard problem together, spread knowledge fast, or onboard new members, and it works remotely.
What it solves
Remote team members work alone on separate tickets, knowledge stays in individual heads, and reviews pile up waiting.
How to run Remote Mob Programming, step by step
- Set one goal for the session, such as a feature, a bug or a document (5 min).
- Join with cameras on. Agree the rotation order and start a ten-minute timer (2 min).
- The first typist shares their screen. The group discusses and tells the typist what to do; the typist does not act on their own ideas (10 min).
- When the timer goes, the typist hands over the work in progress and the next person shares their screen (1 min).
- Repeat the rotation, taking a short break every hour (60-240 min).
- At the end, clean up the work, record key decisions, and do a two-minute check on how the session went (10 min).
Materials needed
- Video call with screen sharing
- Rotation timer
- A fast way to hand over work in progress (a shared branch, file or document)
Facilitator tips
- Keep the group to three to five. Beyond that, individual speaking time drops and people drift off.
- Protect the typist rule. When one person grabs control, the group stops reasoning out loud.
- Meet in person now and then; the originators met monthly to keep relationships strong.
Common pitfalls
- Using a collaborative editor where everyone types, which bypasses the discussion.
- Rotations that are too long, so people lose attention.
Variations
- Mob writing: the same rotation used for writing a strategy document or policy instead of code.
Running it online or hybrid
Everyone must be remote; the originators found that mixing on-site and remote creates information gaps. Cameras on, one shared screen from the current typist, a rotation timer, and a quick hand-over of work in progress between turns.
What it produces
Finished work that everyone in the group understands, plus records of the bigger decisions.
Origin
Developed by Simon Harrer, Jochen Christ and Martin Huber at INNOQ as a remote form of Woody Zuill's Mob Programming, with typist terminology from Mark Pearl's Code with the Wisdom of the Crowd. — source
Build a session around Remote Mob Programming
METODIC places Remote Mob Programming inside a complete, timed session plan — agenda, worksheets, facilitator guide and slides — matched to your group and goal.
Generate a session with Remote Mob Programming · Try METODIC free