Deal with Scope Creep
 
Deal with Scope
Creep
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:
-
Planning for the project. In the
second chapter, the project concept was presented as something that is essential
to get consensus and understanding of purpose, scope, issues, and other factors.
-
Extensive informal communications.
This is stressed in Chapter 9. By communicating with both headquarters and field
locations, you can pick up on potential factors that could affect the
international project.
-
Contingency planning for potential
changes. At the start of the project, you should express the idea that
people will want to make changes. Indicate that this is natural. However, also
tell them that the following questions will have to be addressed. Then when
someone proposes a change ask the questions. It is also a good idea to run
through several examples of change so that they fully understand the process to
be followed.
-
What is the change?
-
What other changes are there?
-
What are the business and political factors behind the
change?
-
What will happen if the change is not carried out in the
project?
-
What will happen if the change is made later after the
project is completed?
-
If the change is made, what will happen to the budget,
schedule, and resources?
-
What are the real benefits of the change?
-
How will the benefits of the change be measured?
-
Will the original benefits of the project be affected if the
change is not made?
-
What will be the role of the person or group that is
suggesting the change? Will they have “skin in the game”?
-
Periodic review of scope. Sit down
with the team and review the project with the view of detecting potential
changes.
856 times read
|
|
|
|