In the world of agile project management (Agile, XP, Lean), many team collaboration techniques emerge that boost efficiency, quality, and flexibility. Some of them – such as pairing, swarming, or mobbing – are not formally described in the PMBOK®, but they are widely used in practice. It’s worth understanding their applications and differences.
Definition: Two developers work together on the same task using one computer.
One — the driver — writes the code.
The other — the observer/navigator — reviews, suggests improvements, and plans ahead.
Goal: Improve code quality, detect errors faster, and promote team learning.
Application: Agile, Extreme Programming (XP).
PMI Status: Informal technique.
Definition: The entire team (or part of it) works together on a single task at one computer.
Goal: Quickly solve complex problems through maximum collaboration.
Difference from pairing: Involves more than two people.
Note: Do not confuse with the psychological term mobbing (workplace bullying).
PMI Status: Informal technique.
Definition: A technique where the team temporarily stops other tasks to focus collectively on one urgent issue.
Features:
Flexible and ad hoc.
Supported by self-organizing teams.
Responds to risks and critical delays.
Application: Scrum, Agile (e.g., toward the end of a sprint).
PMI Status: Recognized practice in the Agile Practice Guide.
Definition: Changing the internal structure of the code without altering its external behavior.Goal: Improve code quality and simplify maintenance.Application: Agile, XP.PMI Status: Informal, but supported in the Agile Practice Guide as part of continuous improvement.
| Technique | Team Size | Number of Tasks | When Used |
|---|---|---|---|
| Pairing | 2 | 1 | Daily programming practice |
| Mobbing | Whole team | 1 | Regularly or for complex tasks |
| Swarming | Several members | 1 | Ad hoc, when one task blocks the sprint |
| Refactoring | 1+ | Multiple | During maintenance or development |
Although techniques like pairing, swarming, mobbing, and refactoring are not formally defined in the PMBOK®, they are practical components of agile teamwork. They support quality, collaboration, faster problem-solving, and continuous product improvement. Understanding these concepts is especially useful when working in Agile environments or preparing for certifications such as PMI-ACP® or PMP®.
mateusz.florczak.96@gmail.com
+48 664-490-214
Website created in a white label responsive website builder WebWave.