Over a million developers have joined DZone.

Old Research Indicates Pair Programming Doesn't Save Time

· Agile Zone

Learn more about how DevOps teams must adopt a more agile development process, working in parallel instead of waiting on other teams to finish their components or for resources to become available, brought to you in partnership with CA Technologies.

Blogger Steven Thomas wanted to base his adoption or non-adoption of pair programming on research.  The best research on the topic that he found was from 6 years ago in Norway.  While the results were underwhelming, I had some thoughts on the research.

First, pair programming's biggest draw is improvement in quality, especially for complex projects where two sets of eyes are better than one.  This Norwegian research used simple projects and complex projects.  The complex projects had a higher success rate, even if it took longer sometimes.  It wasn't always helpful for simple projects, but that's ok. 

Right now, this research is some of the best we have on Pair Programming, but it's not enough of an efficiency booster for Thomas to start using it.  He's happy to look at any other research on professional programmers if readers have any to offer.

Discover the warning signs of DevOps Dysfunction and learn how to get back on the right track, brought to you in partnership with CA Technologies.

Topics:

The best of DZone straight to your inbox.

SEE AN EXAMPLE
Please provide a valid email address.

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.
Subscribe

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}