The case for collaborative programming
Communications of the ACM
The costs and benefits of pair programming
Extreme programming examined
A Discipline for Software Engineering
A Discipline for Software Engineering
Software Inspection
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
Strengthening the Case for Pair Programming
IEEE Software
The Effects of "Pair-Pressure" and "Pair-Learning" on Software Engineering Education
CSEET '00 Proceedings of the 13th Conference on Software Engineering Education & Training
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
Capable Leader and Skilled and Motivated Team Practices to Introduce eXtreme Programming
Balancing Agility and Formalism in Software Engineering
Proceedings of the 2005 conference on Software Engineering: Evolution and Emerging Technologies
PROFES'06 Proceedings of the 7th international conference on Product-Focused Software Process Improvement
Is external code quality correlated with programming experience or feelgood factor?
XP'06 Proceedings of the 7th international conference on Extreme Programming and Agile Processes in 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
Proceedings of the 34th International Conference on Software Engineering
On the effects of pair programming on thoroughness and fault-finding effectiveness of unit tests
PROFES'07 Proceedings of the 8th international conference on Product-Focused Software Process Improvement
| Hi-index | 0.00 |
From the first presentation of extreme programming on, pair programming has attracted a wide range of programmers to work together in front of one display. The proposed advantages of pair programming are a faster development cycle and code with higher quality. However, the nearly doubled personnel cost when compared to single developers seems to outweigh these advantages. Instead of showing the superiority of pair programming, we seek an alternative. Can a single developer be assisted by an already known technique with which he produces the quality of pairs with only a fraction of the cost? The answer with some restrictions is: yes, he can. Reviews are a reasonable candidate with respect to code quality and cost.