The Costs and Benefits of Pair Programming (2000?) Alistair Cockburn, Laurie Williams (University of Utah) http://collaboration.csc.ncsu.edu/laurie/Papers/XPSardinia.PDF
- Through a combination of interviews and controlled experiments, the authors found a range of significant benefits in exchange for a cost in terms of development time of about 15%.
Distributed Pair Programming: An Empirical Study (2004) Brian F. Hanks (University of California, Santa Cruz) http://repositories.cdlib.org/cgi/viewcontent.cgi?article=1713&context=postprints
- This paper reports the results of a controlled experiment using university students in which a collaboration tool enabled remote pairing.
Management Impact on Software Cost and Schedule (1996) Randall W. Jensen http://www.stsc.hill.af.mil/crosstalk/1996/07/manageme.asp
- This article describes a 1975 experiment in 'two person teams' - what we would call pair programming. The technique resulted in significant productivity improvements.
Pair Programming: When and Why It Works (2003) Jan Chong, Robert Plummer, Larry Leifer, Scott R. Klemmer, Ozgur Eris, George Toye http://hci.stanford.edu/research/pairs/PairProgramming-WhenWhy.pdf
- An exploration of the conditions under which pair programming adds value, and how it does so.
Strengthening the Case for Pair Programming (2000) Laurie Williams (North Carolina State University), Robert R. Kessler (University of Utah), Ward Cunningham, Ron Jeffries http://www.cs.utah.edu/~lwilliam/Papers/ieeeSoftware.PDF
- The authors present anecdotal, qualitative, and quantitative evidence of the value of pair programming.
Extracted from StudiesOfAgileEffectiveness
