Scope creep is one of the primary reasons for project failure.
Scope creep refers to uncontrolled changes or growth in the projects scope or deliverables any time after the project is formally authorized. Scope creep occurs when project requirements are not managed.
Consider the following conversation between a project manager and the projects customer:
Customer: “I need you to install updates to 3 more servers.”
Project Manager: “Sure, we can do that for you.”
If the project manager does not write a project change order, he or she just allowed the project scope to creep.
How to Avoid Scope Creep
- Review what is “in scope” and what is “out of scope”. This information can usually be found in the project Charter, the project Scope Statement, or the project Statement of Work
- Challenge any requests for additional work
- Documents all impacts to the approved project Schedule and any Costs
- Log all requests for any requests for changes in the approved project deliverables or schedules
- Do not allow gold plating, that is, inclusion of more than the project scope calls for
- Review all change requests for impacts the approved project schedule or approved project budget
- Consider the impacts or delays to other tasks that are already scheduled
- Estimate the dollar cost and/or additional time required to schedule and implement the requested change
- Get written approval from the customer or project sponsor before agreeing include the change in the project plan
- Be prepared for the customer or project sponsor to reject or defer the requested change
- Communicate the approved or rejected change to the project team and customer
- Don’t forget to update the project plan including the schedule and budget