Mob Programming — What is it?

Mob Programming What is it?

As states:

  • Requirements
  • Testing
  • Designing
  • Bug Fixing
  • Trouble Shooting
  • Testing

Where did it come from?

The original concept comes from Woody Zuill, and the concept was developed by accident. It wasn’t purposely created or applied to solve a particular issue, it was developed of out his belief that “The team doing the work best can figure out how to do the work”. His team began experimenting with new ways of working in 2011 and engaged in training sessions using code kata techniques, originated in the book “Extreme Programming Perspectives” mentioned above. In this technique a small team sit around a screen and take 4 or 5 minutes intervals at the keyboard.

How to set it up?

So the concept is that he entire team sits around one (or two) bug screens, and take turns sitting at the keyboard and everyone works together to solve a problem, develop a user story or whatever the situation might deem.

What are the Benefits?

So what are the benefits? There are many benefits, and these will become obvious depending on the team. But these are some of the universal benefits I can see with using this methodology:


So mob programming is a bit of a buzz word, and its not a silver bullet to solve all team issues, but it is an alternative approach that can be used on occasion to combat issues such as:

  • Team members leaving
  • Decision making
  • Team Moral

About the Author

Ashley-Christian Hardy

Product leader. A strong advocate in innovation, experimentation and building great products with the use of qualitative and quantitative research.