Extreme programming explained: embrace change
Extreme programming explained: embrace change
Hi-index | 0.00 |
One problem of moving development at "Internet speed" is the volatility of requirements. Even in a supposedly stable project like that described here, requirements change as the client sees "targets of opportunity." That is one of the unintended side effects of having the client on-site frequently, although it does increase user satisfaction because they are not prevented from adding functionality. This paper is an account of using an agile method, eXtreme Programming, to survive and manage rapid requirement changes without sacrificing quality.