Mob programming

Mob programming (informally mobbing) is a software development approach where the whole team works on the same thing, at the same time, in the same space, and at the same computer. This is similar to pair programming where two people sit at the same computer and collaborate on the same code at the same time. With mob programming, the collaboration is extended to everyone on the team, while still using a single computer for writing the code and inputting it into the code base.[1]

The basic concept of mob programming is simple: the entire team works as a team together on one task at the time. That is: one team – one (active) keyboard – one screen (projector of course). [2]

— Marcus Hammarberg, Mob programming – Full Team, Full Throttle
French Mob programming session

It builds on principles of lean manufacturing, extreme programming, and lean software development. Early use of the phrase "mob programming" was made in Extreme Programming Perspectives.[3]

In addition to software coding, a mob programming team can work together to do almost all the work a typical software development team tackles, such as defining user stories or requirements, designing, testing, deploying software, and working with the customer and business experts. Almost all work is handled in working meetings or workshops, and all the people involved in creating the software are considered to be team members, including the customer and business experts.[4] Mob programming also works for distributed teams in the same virtual space using screen sharing.[5]

Examples

  • In the book Kanban In Action Sundén and Hammarberg discuss mob programming in relation to the agile process of Limiting Work In Progress [6]
  • Per Jansson on "This is the story about how we in our development team used mob programming as a way to develop software."[7]
  • Mob Programming, and the importance of fun at work discussed at SoCraTes UK 2014[8]
  • Woody Zuill and his team "discovered" programming as a group and it changed their whole process.[9]
  • Dr Simon Harrer and his team do not want to work any other way[10]
gollark: It cheats by basically hibernating.
gollark: It always works fine for me if I press random function keys enough.
gollark: What if it just takes the complement of the set of the people to whom they are attracted?
gollark: ABR is back up.
gollark: I'm running a hyperparameter sweep but I have no idea whether it will help.

See also

References
  1. Zuill, Woody (2014). "Mob Programming: A Whole Team Approach". Agile2014 Conference Experience Reports: 11.
  2. Hammarberg, Marcus. "Mob programming – Full Team, Full Throttle". CodeBetter. CodeBetter. Retrieved 9 September 2014.
  3. Moses Hohman; Andrew Slocum (2003). "Chapter 28. Mob Programming and the Transition to XP". Extreme Programming Perspectives. Addison-Wesley.
  4. Nigri, Julien. "Le Mob Programming : Présentation". Soat (in French). Soat. Retrieved 9 September 2014.
  5. Harrer, Simon; Christ, Jochen; Huber, Martin. "Remote Mob Programming". Retrieved 29 April 2019.
  6. Joakim Sundén; Marcus Hammarberg (2014). Lexleigh, Beth; Kane, Cynthia (eds.). Kanban In Action. Shelter Island, NY: Manning Publications Co. p. 114. ISBN 9781617291050.
  7. Jansson, Per. "Get a good start with mob programming".
  8. Talwar, Samir. "Mob Programming, and the importance of fun at work". Codurance, Craft At The Heart. Codurance LTD. Retrieved 9 September 2014.
  9. Zuill, Woody. "Mob Programming with Woody Zuill". Hanselminutes Podcast. Hanselminutes. Retrieved 20 Feb 2017.
  10. Harrer, Simon. "Remote Mob Programming". Retrieved 7 Jan 2020.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.