- Jul 30, 2017
- 2,114
- 3,318
Scope creep in project management refers to changes, continuous or uncontrolled growth in a project’s scope, at any point after the project begins. This can occur when the scope of a project is not properly defined, documented, or controlled. It is generally considered harmful.Whoa man, calm the scope creep down
If the Wild Life devs make a design document that outlines what Wild Life Sandbox will be precisely from beginning to end, knowing clearly what it will become 3 years from now, they can prevent scope creep from happening. But they're not going that route for sandbox. Instead, they've adopted RAD(Rapid Application Development) style development; a state of prototyping that relies heavily on user feedback, making revisions, repeat. The only problem with this kind of development, you have to constantly be getting detailed and critical feedback from the end user; I'd argue most end users don't know how to give the kind of feedback needed to make RAD work.
Long story short, if you're saying Wild Life devs should draft a design document that outlines what Sandbox will look like 3 years from now, to prevent Scope creep, then I couldn't agree with you more.
So yea, the only reason I'm leaving that kind of feedback, is because that's what their style of development requires, it needs user feedback. Yea, I don't want scope screep either.