Scope creep is an infamous phrase that is as old as projects are. Scope creep can be defined as the unplanned expansion or change of a project after it has been started. How does scope creep arise? Here are some reasons.

• The project was not carefully defined at the start. People just started into planning.

• There was no consensus or agreement on what was to be done in the project. People just assumed. Like the old saying, “Making assumptions makes asses out of you and me.”

• There is lack of communications to detect potential scope creep and change. When change comes, it is often too late to be handled well. Much of the project may have to redone.

• There is no method or approach for dealing with changes. It is all ad hoc, reactive mode—deadly. The project leaders lose control.

Many people accept scope creep as a fact of life in every project. However, it does not have to be this way. If you carefully plan and keep people informed as well as make provisions for dealing with change when it comes, it can be managed better.

Some useful guidelines for dealing with scope creep are the following: