Managing the software process
A Two-Person Inspection Method to Improve Programming Productivity
IEEE Transactions on Software Engineering
The case for collaborative programming
Communications of the ACM
First workshop on economics-driven software engineering research (EDSER-1)
Proceedings of the 21st international conference on Software engineering
Extreme programming explained: embrace change
Extreme programming explained: embrace change
The costs and benefits of pair programming
Extreme programming examined
A Discipline for Software Engineering
A Discipline for Software Engineering
Software Engineering
Recognizing and responding to "bad smells" in extreme programming
Proceedings of the 24th International Conference on Software Engineering
The fourth international workshop on economics-driven software engineering research (EDSER-4)
Proceedings of the 24th International Conference on Software Engineering
Strengthening the Case for Pair Programming
IEEE Software
NextGen eXtreme porting: structured by automation
Proceedings of the 2005 ACM symposium on Applied computing
Investigating the extreme programming system---An empirical study
Empirical Software Engineering
Field Experiences with eXtreme Programming: Developing an Emergency Response System
Journal of Management Information Systems
Controlled experimentation on adaptations of pair programming
Information Technology and Management
A methodology for unit testing actors in proprietary discrete event based simulations
Proceedings of the 40th Conference on Winter Simulation
| Hi-index | 0.00 |
From a project economics point of view, the most important practices of Extreme Programming (XP) are Pair Programming and Test-Driven Development. Pair Programming leads to a large increase in the personnel cost, and Test-Driven Development adds to the development effort. On the other hand, pp can speed the project up, both pp and Tdd can reduce the defect density of the code. Can the increased cost of XP be balanced by its shorter time to market and higher code quality? To answer this question, we construct a new model for the business value of software projects. We then analyze the cost and benefit of XP by applying our model to a realistic sample project. We systematically vary important model parameters to provide a sensitivity analysis. Our analysis shows that the economic value of, XP strongly depends on how large the XP speed and defect advantage really are. We also find that the market pressure is an important factor when assessing the business value of XP., Our study provides clear guidelines for managers when to consider using XP -- or better not.