An Empirical Analysis on the Discontinuous Use of Pair Programming

  title={An Empirical Analysis on the Discontinuous Use of Pair Programming},
  author={Andrea Janes and Barbara Russo and Paolo Zuliani and Giancarlo Succi},
Pair Programming has been shown to increase communication and teamwork skills and to provide better code. The aim of this work is to show the efficacy of Pair Programming in transferring knowledge and skills over an environment where people met only occasionally. In a quasi experiment, we find that Pair Programming is effective in sharing knowledge among 15 students who met once a week for a half day, and did their internship individually or in couple for the remaining 4 half days. 
Qualitative Analysis of Knowledge Transfer in Pair Programming
  • Franz Zieris
  • Computer Science, Business
    2015 IEEE/ACM 37th IEEE International Conference on Software Engineering
  • 2015
Qualitative research is concerned with the analysis of professional software developer's sessions to capture their specific knowledge transfer skill in the form of comprehensible, relevant, and practical patterns.
The True Cost of Pair Programming: Development of a Comprehensive Model and Test
A research model is proposed based on theories and previous empirical studies based on practitioners' experience and perception of the cost of pair programming to identify situations where pair programming is or is not more cost effective than solo programming.
Empirical Studies of Pair Programming for CS/SE Teaching in Higher Education: A Systematic Literature Review
A systematic literature review of empirical studies that investigated factors affecting the effectiveness of pair programming for CS/SE students and studies that measured the effectiveness, showing two clear gaps in this research field, showed a lack of studies focusing on pair compatibility factors aimed at making PP an effective pedagogical tool.
A model of job satisfaction for collaborative development processes
Extreme programming: a survey of empirical data from a controlled case study
  • P. Abrahamsson, Juha Koskela
  • Business
    Proceedings. 2004 International Symposium on Empirical Software Engineering, 2004. ISESE '04.
  • 2004
A survey of the empirical data obtained from a controlled case study on extreme programming in practical settings, which found that no hypotheses were set a priori and the implications of this study are discussed.
Pair Programming and Software Defects--A Large, Industrial Case Study
Investigating the effects of PP on software quality in five different scenarios shows that PP appears to provide a perceivable but small effect on the reduction of defects in these settings.
Extreme programming: first results from a controlled case study
  • P. Abrahamsson
  • Engineering
    2003 Proceedings 29th Euromicro Conference
  • 2003
Analysis shows that while the first release is a learning effort for all stakeholders, the second release shows clear improvement in all regards, e.g., estimation accuracy is improved by 26%, productivity was increased by 12 locs/hour and yet the post-release defect rate remained low, i.e., 2.1 defects/KLoc.
Formal Experimentation for Agile Formal Methods
The methodology needed for conducting formal experiments is presented, related work done in the field of the agile formal methods is reviewed and suggestions on future work in this field of research are suggested.
Empirical Evaluation of Agile Software Development: The Controlled Case Study Approach
Agile software development, despite its novelty, is an important domain of research within software engineering discipline. Agile proponents have put forward a great deal of anecdotal evidence to


Preliminary Analysis of the Effects of Pair Programming on Job Satisfaction
Pair programming is one of the most controversial parts of XP and a questionnaire on pair programming techniques has been compiled and posted on the web, showing a very positive effect of pair programming on job satisfaction.
The costs and benefits of pair programming
It is found that for a development-time cost of about 15%, pair programming improves design quality, reduces defects, reduces staffing risk, enhances technical skills, improves team communications and is considered more enjoyable at statistically significant levels.
Distributed Pair Programming: Empirical Studies and Supporting Environments
The results of the experiment indicate that it is feasible to develop software using distributed pair programming, and that the resulting software is comparable to software developed in colocated or virtual teams.
Strengthening the Case for Pair Programming
It is demonstrated that using pair programming in the software development process yields better products in less time-and happier, more confident programmers.
Distributed eXtreme Programming
This work proposes a crosscutting idea called “Distributed eXtreme Programming” (DXP), which inherits the merits of XP and applies it in a distributed team environment and shows that DXP can be both effective and rewarding in projects whose teams are geographically distributed.
The TAME Project: Towards Improvement-Oriented Software Environments
The TAME system is an instantiation of the TAME software engineering process model as an ISEE (integrated software engineering environment) and the first in a series of Tame system prototypes has been developed.
The Costs and Benefits of Pair Programming Extreme Programming Examined
  • The Costs and Benefits of Pair Programming Extreme Programming Examined
  • 2001
Distributed eXtreme Programming. Proceedings of XP2001 May
  • Distributed eXtreme Programming. Proceedings of XP2001 May
  • 2001