A Discipline for Software Engineering
A Discipline for Software Engineering
Analyzing the Cost and Benefit of Pair Programming
METRICS '03 Proceedings of the 9th International Symposium on Software Metrics
A multiple case study on the impact of pair programming on product quality
Proceedings of the 27th international conference on Software engineering
Introduction to the team software process(sm)
Introduction to the team software process(sm)
Pair-programming effect on developers productivity
XP'03 Proceedings of the 4th international conference on Extreme programming and agile processes in software engineering
Evaluating performances of pair designing in industry
Journal of Systems and Software
Hi-index | 0.00 |
The drawback of pair programming is the nearly doubled personnel cost. The extra cost of pair programming originates from the strict rule of extreme programming where every line of code should be developed by a pair of developers. Is this rule not a waste of resources? Is it not possible to gain a large portion of the benefits of pair programming by only a small fraction of the meeting time of a pair programming session? We conducted a preliminary study to answer this question by splitting the pair programming process into a pair design and a pair implementation phase. The pair implementation phase is compared to a solo implementation phase, which in turn was preceeded by a pair design phase, as well. The study is preliminary as its major goal was to identify an appropriate sample size for subsequent experiments. The data from this study suggest that there is no difference in terms of development cost between a pair and a solo implementation phase if the cost for developing programs of similar level of correctness is concerned.