Analyzing the cost and benefit of pair programming

@article{Padberg2003AnalyzingTC,
  title={Analyzing the cost and benefit of pair programming},
  author={Frank Padberg and Matthias M. M{\"u}ller},
  journal={Proceedings. 5th International Workshop on Enterprise Networking and Computing in Healthcare Industry (IEEE Cat. No.03EX717)},
  year={2003},
  pages={166-177}
}
  • F. Padberg, Matthias M. Müller
  • Published 3 September 2003
  • Computer Science
  • Proceedings. 5th International Workshop on Enterprise Networking and Computing in Healthcare Industry (IEEE Cat. No.03EX717)
We use a combination of metrics to understand, model, and evaluate the impact of pair programming on software development. Pair programming is a core technique in the hot process paradigm of extreme programming. At the expense of increased personnel cost, pair programming aims at increasing both the team productivity and the code quality as compared to conventional development. In order to evaluate pair programming, we use metrics from three different categories: process metrics such as the… 
Modeling the impact of a learning phase on the business value of a pair programming project
TLDR
The authors' simulations show that the cost of the warmup phase is reasonably small compared to the project value, but nonetheless must be taken into account when estimating the project, and suggest that the learning overhead is not an obstacle to introducing and using pair programming in a real environment.
On the Impact of Warmup Phases on the Economics of Pair Programming
TLDR
The net present value model for pair programming is extended to explicitly include a learning interval for pairs and shows that the cost of the warmup phase is small compared to the project value, suggesting that the learning overhead is not an obstacle to introducing and using pair programming.
Effects of pair programming at the development team level: an experiment
TLDR
The pair programming teams wrote code with fewer defects, but were less careful in system testing, and therefore delivered systems with more defects and weak support for higher enjoyment of work in the pair Programming teams is found.
Heterogeneous and homogenous pairs in pair programming: an empirical analysis
TLDR
The empirical analysis between the homogenous and heterogeneous pairs in terms of efficiency, accuracy, quality, quantity of bugs, brainstorming performance and creativity potential during programming activity is presented.
Efficacy of distributed pair programming
TLDR
During the course of this research, the author performed a survey of research studies and experiments conducted to analyze the effects of behavioral factors of programmers on the overall productivity of the pair and quality of the product.
An Empirical Study on Design Quality Improvement from Best-Practice Inspection and Pair Programming
TLDR
Surprisingly, in the study context pair programmers were more effective to find defects in design documents than inspectors, suggesting that when building a larger team for defect detection, a mix of inspection and pair programming can be expected to work better than any single technique.
When the pair programming should be adopted in a business environment
TLDR
The authors of this paper developed 7 controlled experiments and conclude that the pair programming should be adopted only in a business environment to solve problems (programs) complex.
The True Cost of Pair Programming: Development of a Comprehensive Model and Test
TLDR
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.
Analyzing the Cost and Benefit of Pair Programming Revisited
TLDR
This paper focuses on the business aspects of pair programming, by using a number of software development related met rics, such as pair speed advantage, module breakdown structure, of the software and project value discount rate, and augmenting them by taking into account the cost of change after the initial product release and inherent non-linearity of the discount rate curves.
...
1
2
3
4
5
...

References

SHOWING 1-10 OF 13 REFERENCES
On the Economic Feasibility of Pair Programming
This paper provides a summary analysis of pair programming based on the empirical study conducted at the University of Utah [Williams2000]. According to this study, pairs produce higher quality code
Strengthening the Case for Pair Programming
TLDR
It is demonstrated that using pair programming in the software development process yields better products in less time-and happier, more confident programmers.
The costs and benefits of pair programming
TLDR
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.
Embracing Change with Extreme Programming
  • K. Beck
  • Computer Science
    Computer
  • 1999
TLDR
Rather than planning, analyzing, and designing for the far-flung future, XP exploits the reduction in the cost of changing software to do all of these activities a little at a time, throughout software development.
A Two-Person Inspection Method to Improve Prog ramming Productivity
TLDR
A comparison of the models revealed that the experimental group improved significantly in programming speed as a result of using tbe two-person inspection, and it appeared as though this method was more elkctive at improving the performance of the slower programmers.
A discipline for software engineering
  • W. Humphrey
  • Computer Science
    Series in software engineering
  • 1995
Comparative evaluation of software development strategies based on Net Present Value
Assessment of alternative development strategies in a software project can be difficult due to the interactions among the multiple factors involved. A rigorous, value-based approach allows a more
The case for collaborative programming
TLDR
A follow-up field experiment was conducted using experienced programmers who worked on a challenging problem important to their organization, in their own environments, and with their own equipment, and to the surprise of the managers and participants, all the teams outperformed the individual programmers, enjoyed the problem-solving process more, and had greater confidence in their solutions.
Extreme Programming Explained
Extreme Programming (XP) was conceived and developed to address the specific needs of software development conducted by small teams in the face of vague and changing requirements. This new
Managing the software process
  • W. Humphrey
  • Computer Science
    The SEI series in software engineering
  • 1989
TLDR
This work describes the development of a Software Maturity Framework and the Principles of Software Process Change, and describes the management of this framework.
...
1
2
...