Section 5.5.1 Scope Control: Inputs

The project scope statement, along with its associated WBS and WBS dictionary (Section 5.3), defines the project’s scope baseline and product scope.

.2 Work Breakdown Structure

Described in Section 5.3.3.2.

.3 WBS Dictionary

Described in Section 5.3.3.3.

.4 Project Scope Management Plan

Described in Section 5.1.3.1.

.5 Performance Reports

Performance reports provide information on project work performance, such as interim deliverables that have been completed.

.6 Approved Change Requests

An approved change request (Section 4.4.1.4) impacting project scope is any modification to the agreed-upon project scope baseline, as defined by the approved project scope statement, WBS, and WBS dictionary.

.7 Work Performance Information

Described in Section 4.4.3.7.

Section 5.5.2 Scope Control: Tools and Techniques

A project scope change control system, documented in the project scope management plan, defines the procedures by which the project scope and product scope can be changed. The system includes the documentation, tracking systems, and approval levels necessary for authorizing changes. The scope change control system is integrated with any overall project management information system (Section 4.6.2.2) to control project scope. When the project is managed under a contract, the change control system also complies with all relevant contractual provisions.

.2 Variance Analysis

Project performance measurements are used to assess the magnitude of variation. Important aspects of project scope control include determining the cause of variance relative to the scope baseline (Section 5.3.3.4) and deciding whether corrective action is required.

.3 Replanning

Approved change requests affecting the project scope can require modifications to the WBS and WBS dictionary, the project scope statement, and the project scope management plan. These approved change requests can cause updates to components of the project management plan.

.4 Configuration Management System

A formal configuration management system (Section 4.3.2.2) provides procedures for the status of the deliverables, and assures that requested changes to the project scope and product scope are thoroughly considered and documented before being processed through the Integrated Change Control process.

Section 5.5.3 Scope Control: Outputs

If the approved change requests have an effect upon the project scope, then the WBS dictionary is revised and reissued to reflect the approved changes.

Described in Section 5.3.3.4.

.5 Requested Changes

The results of project scope control can generate requested changes, which are processed for review and disposition according to the project Integrated Change Control process.

.6 Recommended Corrective Action

A recommended corrective action is any step recommended to bring expected future project performance in line with the project management plan and project scope statement.

.7 Organizational Process Assets (Updates)

The causes of variances, the reasoning behind the corrective action chosen, and other types of lessons learned from project scope change control are documented and updated in the historical database of the organizational process assets.

.8 Project Management Plan (Updates)

If the approved change requests have an effect on the project scope, then the corresponding component documents and cost baseline, and schedule baselines of the project management plan, are revised and reissued to reflect the approved changes.