An experimental evaluation of the assumption of independence in multiversion programming
IEEE Transactions on Software Engineering
The case for collaborative programming
Communications of the ACM
Strengthening the Case for Pair Programming
IEEE Software
Are Reviews an Alternative to Pair Programming?
Empirical Software Engineering
A multiple case study on the impact of pair programming on product quality
Proceedings of the 27th international conference on Software engineering
Two controlled experiments concerning the comparison of pair programming to peer review
Journal of Systems and Software
Pair-programming effect on developers productivity
XP'03 Proceedings of the 4th international conference on Extreme programming and agile processes in software engineering
Evaluating the effectiveness of VOSDM: a vision oriented approach
ACM SIGSOFT Software Engineering Notes
The Case for Pair Programming in the Computer Science Classroom
ACM Transactions on Computing Education (TOCE)
A groupware system to support collaborative programming: Design and experiences
Journal of Systems and Software
| Hi-index | 0.00 |
Objective: Comparison of program defects caused by programmer pairs and solo developers. Design: Analysis of programs developed during two counter balanced experiments. Setting: Programming lab at University. Experimental units: 42 programs developed by computer science students participating in an extreme programming lab course. Main outcome measures: Programmer pairs make as many algorithmic mistakes but fewer expression mistakes than solo programmers. Results: The second result is significant on the 5% level. Conclusions: For simple problems, pair programming seems to lead to fewer mistakes than solo programming.