Do programmer pairs make different mistakes than solo programmers?

Journal of Systems and Software

Volumn 80, Issue 9, 2007, Pages 1460-1471

  Müller, Matthias M ^a  

^a UNIVERSITY OF KARLSRUHE   (Germany)

Author keywords

Defect comparison; Eureka problems; Pair programming; Solo programming

Indexed keywords

ALGORITHMS; PROBLEM SOLVING; SOFTWARE DESIGN;

ALGORITHMIC MISTAKES; DEFECT COMPARISON; EUREKA PROBLEMS; PAIR PROGRAMMING; SOLO PROGRAMMING;

COMPUTER PROGRAMMING;

EID: 34547770386     PISSN: 01641212     EISSN: None     Source Type: Journal    
DOI: 10.1016/j.jss.2006.10.032     Document Type: Article

References (16)

1. Forsyth D. Group Dynamics. Fourth ed. (2006), Thomson Wadsworth
2. Fowler M. Refactoring: Improving the Design of Existing Code (1999), Addison Wesley
3. Heiberg S., Puus U., Salumaa P., and Seeba A. Pair-programming effect on developers productivity. XP 2003. LNCS vol. 2675 (2003), Springer 215-224
4. Hollander M., and Wolfe D. Noparametric Statistical Methods. Second ed. (1999), John Wiley & Sons
5. Hulkko H., and Abrahamsson P. A multiple case study on the impact of pair programming on product quality. International Conference on Software Engineering (2005), St. Louis, Missouri, USA 495-503
6. Knight C., and Leveson N. An experimental evaluation of the assumption of independence in multi-version programming. IEEE Transactions on Software Engineering 12 1 (1986) 96-109
7. Müller M. Are reviews an alternative to pair Programming?. Journal on Empirical Software Engineering 9 4 (2004) 335-351
8. Müller M. Two controlled experiments concerning the comparison of pair programming to peer review. Journal of Systems and Software 78 (2005) 166-179
9. Müller M. Do programmer pairs make different mistakes than solo programmiers?. Evaluation and Assessment in Software Engineering (EASE) (2006), Keele, UK 69-78
10. Müller M., Link J., Sand R., and Malpohl G. Extreme programming in curriculum: Experiences from academia and industry. Conference on Extreme Programming and Agile Processes in Software Engineering (XP2004) (2004), Garmisch-Partenkirchen, Germany 294-302
11. Nawrocki, J., Wojciechowski, A., 2001. Experimental evaluation of pair programming. In: European Software Control and Metrics (Escom). London, UK.
12. Nosek J. The case for collaborative programming. Communications of the ACM 41 3 (1998) 105-108
13. Steiner I. Group Process and Productivity (1972), Academic Press
14. Tomayko J. A comparison of pair programming to inspections for software defect reduction. Computer Science Education 12 3 (2002) 213-222
15. Weisstein, E., 2006. Gershgorin circle theorem. From MathWorld-A Wolfram Web Resource. http://mathworld.wolfram.com/GershgorinCircleTheorem.html.
16. Williams L., Kessler R., Cunningham W., and Jeffries R. Strengthening the case for pair-programming. IEEE Software (2000) 19-25