Four Antipatterns of Pair Programming

Scrum likes to rely the technical practices recommended by eEXtreme Programming to improve the software quality. Pair programming is one of these practices, even if surveys tell us that it is not used as much as other practices like test-driven development (TDD). In this article, Zee Spencer shares four common pitfalls of pair programming and tell us how to avoid them.

These four common pitfalls are
* Motive Mismatches
* Competence Chasms
* Disposition Dissonance
* Semantic Squabbles

The article explains us that each pitfall presents its own challenges, but it also offers potential benefits if you deal with it effectively. None of them can be solved by avoidance.

Related Content:

Be the first to comment

Leave a Reply

Your email address will not be published.


*