A multiple case study on the impact of pair programming on product quality
Proceedings of the 27th international conference on Software engineering
Confirming the influence of educational background in pair-design knowledge through experiments
Proceedings of the 2005 ACM symposium on Applied computing
Evaluating Pair Programming with Respect to System Complexity and Programmer Expertise
IEEE Transactions on Software Engineering
An experimental investigation of personality types impact on pair effectiveness in pair programming
Empirical Software Engineering
Information and Software Technology
Empirical study on the productivity of the pair programming
XP'05 Proceedings of the 6th international conference on Extreme Programming and Agile Processes in Software Engineering
| Hi-index | 0.00 |
Through his law, "adding manpower to a late software project makes it later," Brooks asserts that the assimilation, training, and intercommunication costs of adding new team members outweigh the associated team productivity gain in the short term. Anecdotes suggest that adding manpower to a late project yields productivity gains to the team more quickly if the team employs the pair programming technique when compared to teams where new team members work alone. We utilize a system dynamics model which demonstrates support of these observations. Parameter values for the model were obtained via a small-scale, non-probabilistic, convenience survey. Our initial findings suggest that managers should incorporate the pair programming practice when growing their team.