- Poor implementation of change control.
- Incomplete gathering of requirements before the beginning of project execution.
- Insufficient involvement of critical stakeholder.
- Lack of support from the executive sponsor.
- Technical scope creep.
- Business scope creep.
The business scope creep occurs due to external forces that may be beyond the control of project manager.An example might be the continual changes in market trends which makes previously defined requirements .One can avoid scope creep by managing the scope of project effectively. There are a number of ways to control or avoid scope creep.They are as follows.
- Involve the costumer and the end users early in the project.
- Introduce a change control board team that would evaluate the risk of implementing the changes.
- Make sure to involve critical stakeholders throughout the project phases.
- Avoid gold plating and gain the ability to refuse changes in requirements with proper reasons and support
- In extreme cases stop the project so that the new additional requirements can be properly scoped and integrated rather than tacked on.
Here we need to make two additional points. They are explained as follows. We need to be careful not to confuse scope creep with progressive elaboration.Progressive elaboration means developing the product in steps and continuing by increments. For example during early strategic planning when information is less defined work packages may be decomposed to the milestone level.As more is known about the upcoming events in the near term they can be decomposed into activities.