Introduction |
---|
Scope change control is concerned
with:
|
5.5.1 Inputs |
---|
|
|
|
|
The WBS defines the project scope baseline.
Performance reports provide interim information on scope performance - which interim products have been completed and which have not. Performance reports may also alert the project team to issues which may cause problems in future.
Change requests may occur in many forms and may require expanding or shrinking of project scope. Most change requests are the result of:
Refer to scope management plan.
A scope change control system defines the procedures by which the project scope may be changed. It includes the paperwork, tracking systems, and approval levels necessary for authorizing changes. The scope change control system should be integrated with the overall change control system.
Performance measurement techniques help to assess the magnitude of any variations which do occur. The important part of scope change control is to determine what is causing the variance and to decide if the variance requires corrective action.
Prospective scope changes may require modification to the WBS or analysis of alternative approaches.
A scope change is any modification to the agreed-upon project scope a defined by the approved WBS. Scope changes often require adjustments to cost, time, quality, or other project activities. These are fed back through the planning process, technical and planning documents are updated as needed and stakeholders notified as appropriate.
This refers to anything done to bring the expected future project performance in line with the project plan.
The causes of variances, the reasoning behind the corrective action chosen, and other types of lessons learned from scope change control should be documented so that this information becomes part of the historical database for both this project and other projects of the performing organization.