||It has been suggested that Scope creep be merged into this article. (Discuss) Proposed since March 2017.|
||This article is written like a personal reflection or opinion essay that states a Wikipedia editor's personal feelings about a topic. (August 2015) (Learn how and when to remove this template message)|
Feature creep, creeping featurism or featuritis is the ongoing expansion or addition of new features in a product, such as in computer software. These extra features go beyond the basic function of the product and can result in software bloat and over-complication rather than simple design.
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 or distribution. However, once the product reaches the point at which it does everything that it is designed to do, the manufacturer is left with the choice of adding unneeded functions, sometimes at the cost of efficiency, or sticking with the old version, at the cost of a perceived lack of improvement.
Another major cause of feature creep might be a compromise from a committee which decides to implement multiple, different viewpoints in the same product. Then, as more features are added to support each viewpoint, it might be necessary to have cross-conversion features between the multiple viewpoints, further complicating the total features.
Product life cycleEdit
At the introduction stage, a manufacturer introduces a new product with a basic feature set (say, a portable cassette player with play, pause, stop, fast forward, rewind, eject) in order to engage the consumer and support use and acceptance; meanwhile, competitors wait[dubious ] and see if the product will create a market worth investing in.
With sufficient growth, competitors enter the space, providing choice to the consumer, often competing merely on price as a cheaper alternative to the flagship brand's product offering.
At the maturity stage, with competitive products occupying the space, new features are introduced ("auto-reverse", "stereo with extra bass", "shock proof for jogging", "waterproof in the rain"...etc.) in order to differentiate brands beyond merely price point, and to create brand demand over price demand. The trailblazer is looking to fend off the new challengers, while the new challengers are looking to get a leg up on the trailblazer. It is at this stage that a proliferation of features occurs most often.
A strong indicator that the maturity stage has been reached, beyond feature creep, is when the trailblazer's prices start to drop in response to the downward pressure from the competition. Some[who?] argue that this occurs when there are no further practical features that can be implemented; this point can be referred to as "feature saturation".
Obsolescence is a primary cause of decline, as time and technology advance beyond the capabilities/value of the incumbent market segment's leading technology. The portable music player platform of the 1980s was cassette; of the 1990s it was CD; in the 2000s the platform was MP3 players; in the 2010s, streaming audio to smartphones predominated; each successive platform shift effectively rendering the previous platform outdated.
There are several methods to control feature creep, including: strict limits for allowable features, multiple variations, and pruning excess features.
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.
Another method of controlling feature creep is to maintain multiple variations of products, where features are kept limited in some variations. Because the ever-growing, ever-expanding addition of new features might exceed available resources, a minimal core "basic" version of a product can be maintained separately, to ensure operation in smaller operating environments. Using the "80/20 Rule" the more basic product variations might support the needs of about "80%" of the users, so they would not be subjected to the complexity (or extra expense) of features requested by the other 20% of users. The extra features are still available, but they have not crept into all versions of the products.
At some point, the cost of maintaining a particular subset of features might become prohibitive, and pruning can be used. A new product version could simply omit the extra features, or perhaps a transition period would be used, where old features were deprecated before eventual removal from the system. If there are multiple variations of products, then some of them might be phased out of use.
Expansion of scopeEdit
Occasionally, uncontrolled feature creep can lead to products far beyond the scope of what was originally intended. However, a more common consequence of feature creep is a delay or cancellation of the product, which almost invariably becomes more expensive than was originally intended.
In gaming, the video game The Elder Scrolls: Arena was originally intended to be a "medieval style gladiator game", but due to feature creep, the game quickly expanded into a large open role-playing game, spawning several sequels. Another example of this is the game Shogun: Total War, which was originally intended to be simply a "B-grade" combat simulation game, but also expanded to produce multiple sequels.
Often, a reasonably feature-complete software project, or one with moderate amounts of feature creep can survive and even thrive through many iterations, but its successor release may suffer substantial delays, once a decision is taken to rewrite the whole code base in addition to introducing new technologies.
Microsoft's Windows Vista was planned to be a minor release between Windows XP and its successor codenamed Windows "Blackcomb", but after adapting more and more features from Blackcomb (many of which were eventually cancelled), Vista turned out to become a major release which took five years of development.
A similar fate was suffered by Netscape 6, which was originally supposed to be Netscape 5. The 1998 decision by Netscape Communications to open-source its Netscape Navigator browser and Communicator internet suite (both code-named Mozilla) soon made it obvious that the underlying code was too difficult, and required a complete rewrite of Mozilla, which fostered the creation of the Mozilla application framework. This caused significant delays, Netscape 5 was skipped, and Netscape the company was purchased by AOL. The subsequent release of Netscape 6.00 in 2000 was widely criticized as alpha-level code, and the project reached stability by Netscape 6.1 in 2001, three years after the decision to rework the Internet suite. By that time, Microsoft's Internet Explorer browser had long-eclipsed Netscape in usage share, which had diminished to single digits.
Even after reaching stability and attaining some necessary new features, the open-source Mozilla Application Suite (then just 'Mozilla'), on which AOL built Netscape, was deemed as bloated, and just a year later a group of Mozilla developers decided to separate the browser component, which eventually became Mozilla Firefox.
Double Fine Adventures' kickstarter project Broken Age is another example of a project being delayed by feature creep. Originally supposed to have a release date of October 2012, the first half of the game was released in January 2014 while the second half followed late April 2015.
Feature creep combined with short deadlines will often lead to a "hacky solution". The desired change may be large enough to warrant a redesign of the existing project foundation, but deadline pressure instead requires to just "make it work" with a less elegant approach. The term "feeping creaturism" was coined to emphasize a developer's dislike of this situation.
|Wikiquote has quotations related to: Featuritis|
- Greenspun's tenth rule
- Mission creep
- Scope creep
- Second-system effect
- Software bloat
- Planned obsolescence
- 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, doi:10.1109/ISTAS.2005.1452719
- Davis, F.D.; Venkatesh, V. (February 2004), "Toward preprototype user acceptance testing of new information systems: implications for software project management", IEEE Transactions on Engineering Management, 51, IEEE Transactions on Engineering Management, issue 1 (1): 31, doi:10.1109/TEM.2003.822468, ISSN 0018-9391
- 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 3-540-42130-0
- Ted Peterson Interview I, By Morrowind Italia, 2001-04-09 - Planet Elder Scrolls
- The Making of: Shogun: Total War, By Kieron Gillen, August 24th, 2007, Rock, Paper, Shotgun
- Double Fine splits Broken Age in half to fund completion, By Kris Ligman, 2013-07-02, Gamasutra
- feeping creaturism, By Denis Howe, 2016-05-27, Dictionary.com - The Free On-line Dictionary of Computing