Scope Control: Change Management | ||||||||||||
 |
|
|
|
|
|
|
|
|
|
|
|
|
 |
||||||||||||
 |
[ Login/Subscribe ] | |||||||||||
 |
||||||||||||
 |
 |
 |
 |
 |
 |
 |
|
 |
||||
 |
||||||||||||
Features
Departments
Executive
Resources
|
Home > Executive Report > Sponsored Content
Scope control remains among the most challenging processes faced by project managers. It requires clarity of definition, precise boundaries, and a reliable change management process.
The rationale for project change control is straightforward. Change control provides a mechanism for identifying change, the impacts of change on critical elements of the project and explicit decisions regarding the change. Project change control primarily focuses on change impacts to the scope, schedule and cost of the project, but also includes attention to the related impacts a change may have on other areas of the project like quality, risk, communications, team, and contracts. The intent of project change control is to make sure that changes are beneficial, not to prevent change.
The natural starting point for any sort of control of changes begins with specific and clear definition of what is expected and agreed, which is why the Work Breakdown Structure (WBS) is a critical input to scope change control. Performance reports are also an important input for change control because they provide a regular checkpoint between plans and reality, therefore a regular opportunity to identify deviations, their causes, consequences and any corrective actions necessary.
The outputs from scope change control include several items, the most notable of which may be adjustments to baselines.
Please login/register to read the entire article.
| |||||||||||||||||
.gif)
|
Privacy Policy Contact Us User Agreement