{"id":721,"date":"2021-12-05T17:06:51","date_gmt":"2021-12-05T17:06:51","guid":{"rendered":"https:\/\/be-agile.agile-world.org\/?p=721"},"modified":"2021-12-05T17:06:51","modified_gmt":"2021-12-05T17:06:51","slug":"mob-programming","status":"publish","type":"post","link":"https:\/\/publicagile.org\/mob-programming\/","title":{"rendered":"Mob Programming"},"content":{"rendered":"

Some teams choose to have all their developers work on solving the same problem simultaneously. Mob programming, or “mobbing” for short, extends the notion of pair programming, often leveraging the driver\/navigator pattern to guide the nature of the interaction. A significant difference is that in pair programming, there is one driver (at the keyboard), and one navigator, while in mob programming<\/a>, there can be more than one navigator, and others might be assisting with research. The benefits of mobbing are similar to pairing, such as higher code quality and increased awareness of the entire code base. Mob programming is also a means of putting the Extreme Programming (XP) practice of collective code ownership into practice, in a systematic way.<\/p>\n

Related Media<\/h3>\n

Mob Programming Video<\/h4>\n

Mob Programming Podcasts<\/h4>\n

Mob Programming Example<\/h4>\n

Related Subjects<\/h3>\n

Collective Code Ownership<\/a><\/p><\/blockquote>\n