Why Won’t They Pair?
I recently wrote an article on Pair Programming over at InfoQ.com. Here is a short excerpt, I hope you head over to their site to continue reading:
Over the past ten years, I worked with over a hundred development teams and they all had one common characteristic: they typically didn’t use pair programming as a technique to deliver software. Some teams talked about pair programming and liked the idea of it, but for some reason(s) they still didn’t pair. This raises the question so why won’t they pair? In my experience there are many obstacles to pair programming and collaboration. Many teams cooperate very well but don’t actually collaborate. Collaboration is a key aspect of pair programming, as it trust.
Pair programming is a technique used in software development where two programmers share one workstation, with one developer called the driver and the other is known as the navigator or observer. The pair take turns using one keyboard to write code and tests. The two developers take turns at the keyboard, giving each person an opportunity to consider the design and appropriate implementation. The pair benefits from the exchange of ideas and typically writes more efficient code.
More Information on Pair Programming
Pair Programming Benefits:
The Collaborative Software Process by Laurie Williams:
Remote Pair Programming video:
How to conduct an interview using pairing:
Survey on Pair Programming Tools:
- Pair Programming Illuminated by Laurie Williams
- The Art of Agile Development: Pair Programming by Jams Shore
- Extreme Programming Explained: Embrace Change, 2nd Edition (The XP Series)Nov 26, 2004 by Kent Beck and Cynthia Andres
- Ensuring the Success of Pair Programming: Critical Personality Traits in Successful Pair Programming by Gülgünes Chomiakow
- Remote Pairing: Collaborative Tools for Distributed DevelopmentDec 12, 2013 by Joe Kutner