Scrum Agile Project Management

Pair Programming Report

August 30, 2012 0

Pair Programming is an Extreme Programming (XP) practice where two developers collaborate on the same code on one workstation. In this blog post, Yan Pritzker provides an experience report after his first nine months of pair programming. On the positive side of pair programming, he lists quick knowledge transfer, improved productivity and higher quality code. The disadvantage of this practice are a tired voices, difficulty to research and learn, need for space for creative activities, longer time spent on trivial tasks, possible issues with sharing the same configuration for the development environment. His conclusion is that “pairing coupled with an extremely pragmatic approach to knowing when not to pair is the key to success.”

Four Antipatterns of Pair Programming

May 23, 2012 0

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.

Does Pair Programming Have to Suck?

March 7, 2012 2

Pair programming is sometimes the norm, and some developers really enjoy the collaboration, experiencing enhanced productivity. In other teams, pairing is shunned, avoided, or… faked. Angela Harms did a short survey about pairing attitudes and compared successful and unsuccessful pairing experiences.

Pair Programming Benefits

February 9, 2012 0

Pair programming is an extreme programming technique that should help Scrum teams to build better software: two heads are better than one, they say, and thus two heads will usually produce a higher-quality system. This article presents the benefits of this technique for the team, the developers and the managers that will appreciate the value of a true team that works well together, collaborates and continuously improves the code base.

1 2