Why Mob Programming - Team Harmony
What is Mob Programming?
Mob programming (hereafter referred to as Mob Pro) is a method where multiple team members work on a single task together. One "Driver" writes the code while multiple "Navigators" collaborate and provide guidance.
The advantages of Mob Pro lie in improved quality and knowledge sharing. Working as a group allows for early detection and resolution of bugs and mistakes. Additionally, sharing ideas and best practices among participants enhances the skill level of the entire team.
However, I will explain the details of Mob Pro in another article. This time, I want to focus on "why I recommend Mob Pro."
The following is my personal perspective. Please take it as a reference.
Why Do I Recommend Mob Pro?
Because I strongly feel that teamwork is crucial for smoothly running a project.
As an engineer, I have experienced both good and bad projects. In projects that went poorly, teamwork was lacking, and when problems arose, someone was often blamed.
When I took on managerial or leadership roles, I made a conscious effort to avoid such situations.
What Does Good Teamwork Look Like?
Sports provide a useful analogy (hopefully). Think of concepts like "ONE TEAM" in rugby or how baseball players support each other after an error or mistake.
Many sports inherently involve capitalizing on the opponent's mistakes to score points. This means that mistakes are a natural part of the game, and constantly blaming or criticizing each other does not foster good teamwork.
I have seen many workplaces where long meetings are held to analyze delays, but if the environment is such that people feel like they are being prosecuted for mistakes, they will hesitate to report delays. By the time problems become apparent, it may be too late to prevent a crisis.
Thus, the correct order of actions is:
- Support teammates when they make mistakes. Say "Don’t worry about it" instead of blaming them.
- Then, as a team, think about how to reduce mistakes in the future.
The first goal should be to create a team where members can openly support each other.
The Opposite of Mob Pro: The Reality of Solo Work
I feel that the IT industry is somewhat unusual in this regard (personal opinion).
Engineers are often assigned to projects based on their programming language expertise or front-end experience. Once assigned, they are given documentation on business knowledge and project history and are expected to start working immediately.
As a Software Engineering Services (SES) employee, I used to feel very anxious when joining a new project.
How About Other Industries?
This would be unimaginable for firefighters or doctors. Even if they have undergone training, firefighters are never sent alone to a burning building, and doctors spend years training alongside experienced professionals.
In professions requiring advanced skills or dealing with high-risk situations, this level of preparation is standard practice.
However, in IT, the culture seems to accept "working on tasks alone" as the norm. I have never been in a workplace where someone said, "I’m always here to help, so feel free to ask anything."
That’s Why Mob Pro
Once I learned about Mob Pro, I felt this should be the standard approach in daily work.
First, the team works together, aligning their understanding and solving problems collectively. Once all members reach a consensus, the task is complete—meaning review is also complete—thus ending the mob session.
A highly efficient process.
Of course, Mob Pro is not a silver bullet and does not solve every problem. However, it allows teams to decide whether to continue with Mob Pro or shift to solo work after an initial session. It can also be used flexibly as needed.
Ultimately, teamwork is what matters most. I would be happy if more people recognize Mob Pro as one effective way to achieve it.