However, at enterprise scale, the challenge is quite different. For example, in one agile project that was recently completed by a large product business unit, the first release of a large-scale systems development project took 250 people approximately 9 months to complete. The costs and market delays to spend the many months refactoring that application are clearly prohibitive. Moreover, since the application is deployed in the field, any substantive rework would necessitate a large-scale field upgrade, which would be expensive to the producer, disruptive to the customer, and worse, likely to induce new defects that were not present in the earlier release. (And we all know that regressing customers with new defects in existing code i...
- Chapter 16. Intentional Architecture
- from Scaling Software Agility: Best Practices for Large Enterprises
- Publisher: Addison-Wesley Professional
- Released: February 2007
This is a controversial approach, it describe a big refactoring at the end indeed isn't feasible.
Share this highlighthttp://www.safaribooksonline.com/a/scaling-software-agility/4155684/