Modeling the Impact of a Learning Phase on the Business Value of a Pair Programming Project
Authors:
- M.M. MullerMMM.M. Muller
- 5 April 2005
- conference paper
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- p. 142-149
Abstract
Pair programmers need a "warmup phase" before the pair can work at full speed. The length of the learning interval varies, depending on how experienced the developers are with pair programming and how familiar they are with each other. We study how large the impact of the lower pair productivity during warmup is on the business value of the pair programming project. To this end, we extend our net present value model for pair programming to explicitly include a learning interval for pairs. We then carry out a simulation study where we vary the shape of the learning curve, the length of the learning interval, the final productivity level of the pairs, the market pressure, and the size of the workforce. Our 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. Our results also suggest that the learning overhead is not an obstacle to introducing and using pair programming in a real environment.Keywords
This publication has 9 references indexed in Scilit:
- Case study: extreme programming in a university environment2005
- Building pair programming knowledge through a family of experiments2004
- Analyzing the cost and benefit of pair programming2004
- Extreme Programming in Curriculum: Experiences from Academia and Industry2004
- Strengthening the case for pair programmingIEEE Software, 2000
- The case for collaborative programmingCommunications of the ACM, 1998
- A learning curve primer for software engineersACM SIGSOFT Software Engineering Notes, 1996
- Computational survey of univariate and multivariate learning curve modelsIEEE Transactions on Engineering Management, 1992
- A Two-Person Inspection Method to Improve Prog ramming ProductivityIEEE Transactions on Software Engineering, 1989