This page is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
I added this article after noticing that the term was included in this article and might be confusing to the reader. User:Theoldanarchist noted that this is a neologism which is irrelevant to this article. I agree and this is the reason I migrated it over to a sub article. The criteria for a disambig link is much lower however: as I understand the policy a page only needs to have a high likelihood of being confused with another term to merit a link or disambiguation page. In this case, it is impossible for someone searching for the alternate definition of the term to find it because 'scope creep' will direct them here. Whether the definition itself is wikiworthy is another issue and could be taken up with an AfD nomination. See WP:D for policy details.
Hi Just to let you know that i've added a lot more content to this page and added quite a number of citations/sources. Would it be possible for you to re-check the page? Thanks {Dianogah 15:55, 17 November 2006 (UTC)}
This article currently seems to suggest that "Scope Creep" only means "Growing Scope", that is, the customer expects more and more requirements to be implemented. I experience the opposite in the current project: the supplier increasingly delcares requirements as "out of scope". How does it correspond to this antipattern? Is there a dedicated antipattern for that? —The preceding unsigned comment was added by 62.180.31.65 (talk) 07:07, 24 January 2007 (UTC).
Functionality Creep is the process where technologies and processes are used for purposes not intended, or when the technologies and processes evolve into a new identity from a form with a lessor function. This is not Scope Creep. Scope Creep may fall under the category of Functionality Creep. Functionality Creep should have its own Wikipedia page, as before this series of redirects from Featuritis to Scope Creep. Perhaps there is a more pervasive, elusive process at work here that contiues to misidentify and mislabel the Functionality Creep concept. Perhaps Functionality Creep is an adventursome, catastrophic principle on the cutting edge of human thought that has yet to see its banner unfurled in full rendition. That may explain how well-meaning Wikipedians continue to misappropriate the unfortunate case of Functionality Creep. Kreepy krawly 19:41, 13 February 2007 (UTC)
if you can do it in 2 steps why to do it 20 ? this entry is more about : if you do not even know where in the "feature rich" mess a controll/command can be. Like being hashed by a function and then search original value. Hashing is one way relation. One should reflect, create relation both ways. Why is it i never see relation to graphs in wikipedia? Data structures are graphs. Control structures are graphs of flow. Programs are made from them. And is it worth tranforming those non-exact articles to more exact (simpler!) form ? I do not think there should be rich mathematical formulas. But if you understand some basic you should see the mappings (again graph :) ). Xchmelmilos (talk) 17:50, 22 December 2007 (UTC)
should a referenced real-life example of this phenomenon be included in the article or not?
Maybe the article could quote itself as an example? Martin Hogbin (talk) 00:17, 21 December 2010 (UTC)