The case for collaborative programming
Communications of the ACM
Extreme programming explained: embrace change
Extreme programming explained: embrace change
The costs and benefits of pair programming
Extreme programming examined
Case study: extreme programming in a university environment
ICSE '01 Proceedings of the 23rd International Conference on Software Engineering
A Discipline for Software Engineering
A Discipline for Software Engineering
Pair Programming Illuminated
Strengthening the Case for Pair Programming
IEEE Software
Pair programming and pair trading: effects on learning and motivation in a CS2 course
Journal of Computing Sciences in Colleges
Exploring XP for Scientific Research
IEEE Software
New directions on agile methods: a comparative analysis
Proceedings of the 25th International Conference on Software Engineering
The impact of pair programming on student performance, perception and persistence
Proceedings of the 25th International Conference 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
Integrating Pair Programming into a Software Development Process
CSEET '01 Proceedings of the 14th Conference on Software Engineering Education and Training
Using a Coding Standard to Improve Program Quality
APAQS '01 Proceedings of the Second Asia-Pacific Conference on Quality Software
The collaborative software process(sm)
The collaborative software process(sm)
Building Pair Programming Knowledge through a Family of Experiments
ISESE '03 Proceedings of the 2003 International Symposium on Empirical Software Engineering
An Initial Framework for Research on Pair Programming
ISESE '03 Proceedings of the 2003 International Symposium on Empirical Software Engineering
Coupling pair programming and writing: learning about students' perceptions and processes
Proceedings of the 35th SIGCSE technical symposium on Computer science education
An Initial Exploration of the Relationship Between Pair Programming and Brooks' Law
ADC '04 Proceedings of the Agile Development Conference
Mobile-D: an agile approach for mobile application development
OOPSLA '04 Companion to the 19th annual ACM SIGPLAN conference on Object-oriented programming systems, languages, and applications
Investigating the extreme programming system---An empirical study
Empirical Software Engineering
Evaluating performances of pair designing in industry
Journal of Systems and Software
The Social Dynamics of Pair Programming
ICSE '07 Proceedings of the 29th international conference on Software Engineering
Do programmer pairs make different mistakes than solo programmers?
Journal of Systems and Software
Proceedings of the 2008 symposium on Eye tracking research & applications
Pair programming: what's in it for me?
Proceedings of the Second ACM-IEEE international symposium on Empirical software engineering and measurement
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
ESEM '09 Proceedings of the 2009 3rd International Symposium on Empirical Software Engineering and Measurement
A preliminary study on the impact of a pair design phase on pair programming and solo programming
Information and Software Technology
Test case selection and prioritization: risk-based or design-based?
Proceedings of the 2010 ACM-IEEE International Symposium on Empirical Software Engineering and Measurement
Integrating the google wave platform with eclipse for collaborative, real-time code creation
Proceedings of the 2010 ACM conference on Information technology education
Software evolution in agile development: a case study
Proceedings of the ACM international conference companion on Object oriented programming systems languages and applications companion
Towards a process for architectural modelling in agile software development
Proceedings of the joint ACM SIGSOFT conference -- QoSA and ACM SIGSOFT symposium -- ISARCS on Quality of software architectures -- QoSA and architecting critical systems -- ISARCS
PROFES'06 Proceedings of the 7th international conference on Product-Focused Software Process Improvement
Lessons learned from an XP experiment with students: test-first needs more teachings
PROFES'06 Proceedings of the 7th international conference on Product-Focused Software Process Improvement
Empirical Software Engineering
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
SCRUM and productivity in software projects: a systematic literature review
EASE'10 Proceedings of the 14th international conference on Evaluation and Assessment 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
Disengagement in pair programming: does it matter?
Proceedings of the 34th International Conference on Software Engineering
Proceedings of the 34th International Conference on Software Engineering
DroidSense: a mobile tool to analyze software development processes by measuring team proximity
TOOLS'12 Proceedings of the 50th international conference on Objects, Models, Components, Patterns
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
A groupware system to support collaborative programming: Design and experiences
Journal of Systems and Software
| Hi-index | 0.00 |
Pair programming is a programming technique in which two programmers use one computer to work together on the same task. There is an ongoing debate over the value of pair programming in software development. The current body of knowledge in this area is scattered and unorganized. Review shows that most of the results have been obtained from experimental studies in university settings. Few, if any, empirical studies exist, where pair programming has been systematically under scrutiny in real software development projects. Thus, its proposed benefits remain currently without solid empirical evidence. This paper reports results from four software development projects where the impact of pair programming on software product quality was studied. Our empirical findings appear to offer contrasting results regarding some of the claimed benefits of pair programming. They indicate that pair programming may not necessarily provide as extensive quality benefits as suggested in literature, and on the other hand, does not result in consistently superior productivity when compared to solo programming.