Feature creep is the proliferation of features in a product such as computer software.[1] These often go beyond the basic function of the product and so can result in baroque over-complication rather than simple, elegant design.
Causes
The most common cause is the desire to provide the consumer with a more useful or desirable product, in order to increase sales. However, the point often comes where a product does everything it's expected to do, leaving the manufacturer with the choice of adding unneeded functions or sticking with the old product.
Characteristics
Feature creep is the most common source of cost and schedule overruns.[2] It thus endangers and can even kill products and projects. Apple's abandoned Copland operating system is an example of this.
Control
Feature creep may be actively controlled by rigorous change management and by delaying changes to later delivery phases of the project.[3] An amusing method of controlling featuritis was presented by Crytek CEO who explained that people working at the company constantly proposing new features were forced to wear a badge that read "Feature Creep".[4]
See also
Mitigation
References
- ^ J.M. Sullivan (8-10 June 2005), Impediments to and incentives for automation in the Air Force, pp. 101-110, <http://ieeexplore.ieee.org/xpl/freeabs_all.jsp?arnumber=1452719>
- ^ Davis, F.D. and Venkatesh, V. (February 2004), Toward preprototype user acceptance testing of new information systems: implications for software project management, 51 issue 1, IEEE Transactions on Engineering Management, ISSN 0018-9391, <http://ieeexplore.ieee.org/xpl/freeabs_all.jsp?arnumber=1266852>
- ^ Kenneth S. Norton (2001), Applying Cross-Functional Evolutionary Methodologies to Web Development, paper in Web Engineering: Managing Diversity and Complexity of Web published by Springer, ISBN 3540421300, <http://books.google.co.uk/books?id=Ak5slktYul8C>
- ^ Crytek - A játékgrafika jövõje - Cevat Yerli, GDF Hunary
External links
|
