Feature creep: Difference between revisions
invalid citation source |
|||
| Line 1: | Line 1: | ||
{{for|the project management concept|scope creep}} |
{{for|the project management concept|scope creep}} |
||
'''Feature creep''' |
'''Feature creep''' is the proliferation of features in a product such as [[computer software]].<ref> |
||
{{cite web |
|||
|url= http://www.catb.org/jargon/html/F/feeping-creaturism.html |
|||
|accessdate= 2008-08-04 |
|||
|title= Feeping Creaturism |
|||
|work= The Jargon File |
|||
}}</ref>) is the proliferation of features in a product such as [[computer software]].<ref> |
|||
{{citation |
{{citation |
||
|title= Impediments to and incentives for automation in the Air Force |
|title= Impediments to and incentives for automation in the Air Force |
||
Revision as of 17:52, 12 November 2008
Feature creep is the proliferation of features in a product such as computer software.[1] Extra features 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 of feature creep is the desire to provide the consumer with a more useful or desirable product, in order to increase sales. However, once the point at which a product does everything that it is expected to do is reached, the manufacturer is left 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
Temptation of later feature creep may be avoided to some degree by basing initial design on strong software fundamentals such as logical separation of functionality and data access. It can be actively controlled with rigorous change management and by delaying changes to later delivery phases of a project.[3]
See also
Mitigation
References
- ^
J.M. Sullivan (8–10 June 2005), "Impediments to and incentives for automation in the Air Force", 2005 International Symposium on Technology and Society, pp. 101–110
{{citation}}: CS1 maint: date format (link) - ^ Davis, F.D. and Venkatesh, V. (February 2004), Toward preprototype user acceptance testing of new information systems: implications for software project management, vol. 51 issue 1, IEEE Transactions on Engineering Management, ISSN 0018-9391
{{citation}}: CS1 maint: multiple names: authors list (link) - ^ 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