ACM Home Page
Please provide us with feedback. Feedback
Pair programming: what's in it for me?
Full text PdfPdf (432 KB)
Source
ESEM archive
Proceedings of the Second ACM-IEEE international symposium on Empirical software engineering and measurement table of contents
Kaiserslautern, Germany
SESSION: From the programmers' trenches table of contents
Pages 120-128  
Year of Publication: 2008
ISBN:978-1-59593-971-5
Authors
Andrew Begel  Microsoft, Redmond, WA, USA
Nachiappan Nagappan  Microsoft, Redmond, WA, USA
Sponsors
SIGSOFT: ACM Special Interest Group on Software Engineering
ACM: Association for Computing Machinery
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 37,   Downloads (12 Months): 242,   Citation Count: 0
Additional Information:

abstract   references   index terms   collaborative colleagues  

Tools and Actions: Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1414004.1414026
What is a DOI?

ABSTRACT

Pair programming is a practice in which two programmers work collaboratively at one computer on the same design, algorithm, or code. Prior research on pair programming has primarily focused on its evaluation in academic settings. There has been limited evidence on the use, problems and benefits, partner selection, and the general perceptions towards pair programming in industrial settings. In this paper we report on a longitudinal evaluation of pair programming at Microsoft Corporation. We find from the results of a survey sent to a randomly selected 10% of engineers at Microsoft that 22% pair program or have pair programmed in the past. Using qualitative analysis, we performed a large-scale card sort to group the various benefits and problems of pair programming. The biggest perceived benefits of pair programming were the introduction of fewer bugs, spreading code understanding, and producing overall higher quality code. The top problems were cost-efficiency, (work time) scheduling problems, and personality conflicts. Most engineers preferred a partner who had complementary skills to their own, who was flexible and had good communication skills.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
 
2
 
3
 
4
 
5
 
6
C. Bishop-Clark and D. D. Wheeler, "The Myers-Briggs personality type and its relationship to computer programming", Journal of Research on Computing in Education, 26(3), pp. 358--370, Spring 1994.
 
7
 
8
9
10
11
12
 
13
 
14
M. M. Müller and O. Hagner, "Experiment about Test-first Programming", Proceedings of Conference on Empirical Assessment in Software Engineering (EASE), pp. 2002.
15
 
16
N. Nagappan, L. Williams, E. Wiebe, C. Miller, S. Balik, M. Ferzli, and J. Petlick, "Pair Learning: With an Eye Toward Future Success", Proceedings of Extreme Programming/Agile Universe, New Orleans, pp. 2003.
 
17
J. Nawrocki and A. Wojciechowski, "Experimental Evaluation of Pair Programming", Proceedings of European Software Control and Metrics (ESCOM 2001), London, England, pp. 2001.
 
18
 
19
 
20
 
21

Collaborative Colleagues:
Andrew Begel: colleagues
Nachiappan Nagappan: colleagues