A scope change request is used to request an addition or subtraction to the agreed upon scope of work agreed upon for a project. Scope change requests may be managed as part of a pre-defined scope change process outlined as part of the Project plan. This process would determine what changes may be approved by the Project Manager and the procedure as well as authority for approving other changes.
The success of a project depends on controlling and managing the scope. Changes in scope can impact the cost, schedule, risk and even the quality of the project. The client, the project sponsor or other stakeholders can initiate scope changes. The scope of work is defined very early in the project planning and estimation phases. However, scope can change for a number of reasons including internal factors (stakeholder requires insight into a problem), or external factors (government regulations, market conditions). For example, the ABC Corporation engages a firm to install a new network. In the middle of the project, ABC purchases the Acme Corporation and now needs to add them to the project. This would change the cost, schedule and resources of the project. Another example of scope change is other initiatives within the organization change resulting in revised needs for the project, such as a new billing system has been installed thus an interface that is part of the project must be changed. Inevitably, change does happen and project managers must be able to effectively practice project scope management.
The key to successful scope management is defining, communicating and reconciling emerging requests throughout the project lifecycle. Many projects have failed due to the failure to manage scope change. When a project's scope changes mid-course it will typically mean added costs, resources, time, extended duration and greater risks. Sometimes it is a number of small scope changes that impact the successful completion of a project rather than one large scope change.
Project Management
Project Plan
|