A Two-Person Inspection Method to Improve Programming Productivity
IEEE Transactions on Software Engineering
The case for collaborative programming
Communications of the ACM
Building Knowledge through Families of Experiments
IEEE Transactions on Software Engineering
IEEE Transactions on Software Engineering
IEEE Transactions on Software Engineering
A Discipline for Software Engineering
A Discipline for Software Engineering
The effects of pair-programming on performance in an introductory programming course
SIGCSE '02 Proceedings of the 33rd SIGCSE technical symposium on Computer science education
Ethical Issues in Empirical Studies of Software Engineering
IEEE Transactions on Software Engineering
The Effects of "Pair-Pressure" and "Pair-Learning" on Software Engineering Education
CSEET '00 Proceedings of the 13th Conference on Software Engineering Education & Training
The Development and Evaluation of Three Diverse Techniques for Object-Oriented Code Inspection
IEEE Transactions on Software Engineering
Analyzing the Cost and Benefit of Pair Programming
METRICS '03 Proceedings of the 9th International Symposium on Software Metrics
An Empirical Study about the Feelgood Factor in Pair Programming
METRICS '04 Proceedings of the Software Metrics, 10th International Symposium
Introduction to the team software process(sm)
Introduction to the team software process(sm)
Evaluating Pair Programming with Respect to System Complexity and Programmer Expertise
IEEE Transactions on Software Engineering
Do programmer pairs make different mistakes than solo programmers?
Journal of Systems and Software
Pair programming in software development teams - An empirical study of its benefits
Information and Software Technology
Capable Leader and Skilled and Motivated Team Practices to Introduce eXtreme Programming
Balancing Agility and Formalism in Software Engineering
An experimental investigation of personality types impact on pair effectiveness in pair programming
Empirical Software Engineering
Inspecting automated test code: a preliminary study
XP'07 Proceedings of the 8th international conference on Agile processes in software engineering and extreme programming
Test-driven roles for pair programming
Proceedings of the 2010 ICSE Workshop on Cooperative and Human Aspects of Software Engineering
Do programmer pairs make different mistakes than solo programmers?
EASE'06 Proceedings of the 10th international conference on Evaluation and Assessment in Software Engineering
Hi-index | 0.00 |
This paper reports on two controlled experiments comparing pair programming with single developers who are assisted by an additional anonymous peer code review phase. The experiments were conducted in the summer semester 2002 and 2003 at the University of Karlsruhe with 38 computer science students. Instead of comparing pair programming to solo programming this study aims at finding a technique by which a single developer produces similar program quality as programmer pairs do but with moderate cost. The study has one major finding concerning the cost of the two development methods. Single developers are as costly as programmer pairs, if both programmer pairs and single developers with an additional review phase are forced to produce programs of similar level of correctness. In conclusion, programmer pairs and single developers become interchangeable in terms of development cost. As this paper reports on the results of small development tasks the comparison could not take into account long time benefits of either technique.