Home
/
Ressources
/
Blog
/
Tech trends
/
Mob Programming During a Pandemic: Lessons Learned
Blog article

Mob Programming During a Pandemic: Lessons Learned

Julien Mege
July 7, 2026
Updated on
July 6, 2026
4
min read

This article offers my thoughts on the benefits of mob programming, and how the Bonitasoft development team adapted to continue even through the Covid-19 office closures.

What is mob programming?

Mob programming is a software development approach where an entire team gathers around one keyboard and one projector screen at once, according to Agile community organization Agile Alliance. It’s an extension of pair programming, which involves two team members collaborating to complete a development task in the same space.

Embracing Mob Programming

My five-person team is responsible for the development of the Bonita platform portal for delivery of applications. We tried a mob programming approach to design and test an application page, a medium complexity project built with Gradle, using the Bonita UI Designer web page development tool and tested with Cypress.

The team worked on a laptop and a standard-size screen in the open office space. Pros: Fast development completion, better implementation and good test coverage. Cons: Decreased focus because of lengthy discussion and the distraction of phone notifications, communication style differences and paused cross-cutting topics.

My team members and I loved the result of mob programming but needed to iron out some issues. 

Among other adjustments, we moved to a quieter spot in the office to work. We swapped out the small screen for a giant screen and replaced the laptop with a desktop, keyboard and mouse. We scheduled more breaks. We adhered to the basic rules. We rotated roles every 15 minutes, which meant all team members were more attentive and involved. Recognizing that timid team members might not speak up, we distributed speaking time more fairly. And we were more selective when choosing projects for the mob programming method (bug fixes, for instance, are best solved through pair programming).

How We Benefited from Mob Programming

The process required a little tweaking at the beginning but it was well worth it. Here are some of the mob programming benefits we realized:

  • We moved quickly on the development project
  • We eliminated merge conflicts
  • We spent less time in standup meetings and pull request reviews
  • We had fewer external interruptions (people are less willing to interrupt an entire group than just one person working independently).
  • Our knowledge sharing improved. All members of a mob programming development team receive the same level of knowledge on new developments. New team members are able to quickly ramp up on the legacy code.
  • The solutions we developed were better tested with fewer bugs in the final product. Since the code is made modularly, it’s easy to modify if needed.
  • Mob programming has taught us to communicate in a way that works best for each team member. We appreciate the diversity of thought and personality among team members rather than viewing it as a disadvantage.

Can Mob Programming Work in a Pandemic?

Bonitasoft devs are all working remotely. We apply the basic rules using videoconferencing tools, and duplicate the development environment for everyone. Communicating via videoconferencing was an adjustment but it works. Each team can adapt mob programming to what works best for them over multiple iterations, whether they’re working in the same space or remotely.

Here are a few mob programming tips:

  • Define when it involves remote work versus when it will involve everyone working in the same space (with social distancing procedures in place, of course).
  • Apply the basic rules strictly, so you have a solid foundation on which to build a mob programming practice.
  • Limit potential distractions by opting for a large screen, mouse and keyboard in a quiet location.
  • Factor free time into your non-sprint work schedule so that team members can check their email and work on other projects.
  • Define break times (the Pomodoro technique could be one option).

Mob Programming is Worth Exploring … Even Now!

At Bonitasoft, smart implementations have resulted from the development team embracing the value of collective intelligence and mob programming. We’re delivering projects faster and enjoying greater satisfaction in our work lives. With some adaptation, it’s possible to realize its value by adding it to any team's development methodology options.

 

Read the entire article by Julien, originally published on DevOps.com, here: https://devops.com/mob-programming-during-a-pandemic-lessons-learned/

Ready to orchestrate your AI operations?

Schedule a personalized demo and see how Ofelia can transform your AI infrastructure.

Obtenir une démo
Julien Mege

Questions fréquentes
Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam.
Quels types de partenaires sont référencés ici ?
Des cabinets de conseil, intégrateurs systèmes et spécialistes en implémentation qui aident les organisations à déployer Ofelia et à le connecter à leurs outils et processus existants. Ils apportent le contexte, les relations et l'expertise pour transformer un déploiement en impact opérationnel réel.
Comment choisir le bon partenaire pour mon projet ?
Regardez leur focus sectoriel et leur bilan de livraison. Le bon partenaire travaille déjà dans des environnements comme le vôtre. Il a géré les contraintes de conformité, les systèmes legacy, les dynamiques internes. Pas sûr par où commencer ? Nous vous aidons à trouver le bon profil — contactez-nous et nous vous orientons.
Un partenaire peut-il m'aider à définir par où commencer ?
Oui. La plupart des partenaires mènent une phase de cadrage avant tout déploiement. Ils identifient les workflows qui créent le plus de friction et définissent où vous obtenez des résultats en premier. Vous n'avez pas besoin d'un cahier des charges. Vous avez besoin d'une conversation.
Combien de temps faut-il pour passer en production ?
Premier workflow en jours, pas en mois. Aucun projet d'infrastructure, aucun sprint IT dédié. Le process owner pilote le déploiement.
Y a-t-il une taille minimale pour travailler avec un partenaire ?
Non. Ce qui compte, c'est le défi opérationnel — pas l'effectif. Les partenaires travaillent aussi bien avec des entreprises en forte croissance qu'avec de grands groupes.