Part 6 of 6: Wrap Up
In this last part of this series on scope control best practices, we will review the major points to remember.
Scope Control and Scope Creep
Scope control is defined as:
“The process of monitoring the status of the project scope and managing changes to the scope baseline”
and scope creep as:
“The uncontrolled expansion to project scope without adjustments to time, costs and resources”
So scope changes are OK, as long as they are managed. Scope creep however is a no no for us.
Control Scope Throughout All Project Phases
For scope control to be effective, it must be applied throughout all phases of a project. Scope control starts in the initiation phase and should be applied all the way to the closing phase of a project.
Have a Change Request Procedure in Place
During a project you will receive many change requests. Since any approved change request will usually effect your schedule and budget, it should be properly documented. A change request form should be used to properly and consistently document all change requests. A change request form should contain the following items:
- CHANGE REQUEST N0.
- CHANGE REQUEST DESCRIPTION
- REQUESTED BY
- EFFECT ON DOCUMENT(S)
- EFFECT ON COMPLETION DATE
- COST CONSEQUENCES
- REQUESTOR’S SIGNATURE
- PROJECT MANAGER’S SIGNATURE
- DATE APPROVED
Process Change Request ASAP
Change requests should be documented as soon as possible. Do this to avoid time and costs consequence surprises at the end of the project.
Document the Change Request Procedure in Your Contracts
The change request procedure should be an article in your contract stating that change requests should be requested making use of the included change request form and approved before the work is initiated.