Recently, we had a project due at the end of the month, but due to "scope creep" that was outside our control on another initiative, the project had to be delayed.
If the requirements are loosely defined, then consider the risk of scope creep exponentially increased.
In particular, the area of security posed a huge opportunity for scope creep, so we had to work closely with ASDI to understand exactly what their security needs were.
As the definition above stated, the fundamental cause of scope creep more often than not revolves around requirements.
This is important because it helps to avoid "scope creep," the addition of new requirements as the project progresses.
With scope creep, a series of small changes - none of which appear to affect the project individually - can accumulate and have a significant overall impact on the project.
I have seen some extremely detailed requirements documents that don't help avoid scope creep.
What is scope creep?
國文精選館
