Talk:Scope creep
From Wikipedia, the free encyclopedia
Contents |
[edit] Disambig to Scope creep (relationships)
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.
[edit] Sputniks Down
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)}
[edit] Scope Creep = Growing Scope?
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).
- Scope creep is the process of the project requirements expanding while the project is underway--for example, "Oh, PDF 1.7 just came out, can you support the new feature set?", asked halfway through development, would be a case of scope creep. In your case, either you're trying to creep the scope, by asking for things that were not explict in the original requirements, or they're trying to scale back the project because they're in over their heads. Either way, it just goes to show that you should be as explict as possible in the contract, to leave the minimum possible room for misunderstanding. scot 20:05, 13 February 2007 (UTC)
[edit] Functionality Creep should not be redirected to Scope Creep
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)
- I see what you mean with functionality creep; "When all you have is a hammer, every problem becomes a nail" sums it up, I think. I'm not sure I agree that this is synonymous with featuritis, I see featuritis is a hybrid of the two. When someone says "I want to be able to write Word documents in my web browser", it's not a case of using the browser for something it wasn't intended; someone has to deliberately add that ability, that's what makes it featuritis. Functionality creep is me using my "extract details from shadow" algorithm, with a negative image function before and after, to extract details from washed out areas. I didn't write the algorithm to do that, but I didn't have to change it to use it differently, I just had to use it differently. scot 20:05, 13 February 2007 (UTC)
