According to the PMBOKĀ® Guide, the Control Scope process is the process of monitoring the status of the project and product scope and managing changes to the scope baseline. To perform this process accurately, several components of the project management plan and various project documents are required as inputs.
While it may seem counterintuitive, the Project Schedule is a formal input to Control Scope because scope and schedule are inextricably linked.
Baseline Alignment: The schedule shows when specific deliverables (scope) are expected to be completed.
Impact Analysis: When a scope change is proposed or a variance is detected, the project manager must refer to the schedule to see how the change in work volume affects the timeline.
Integrated Control: In the PMI framework, you cannot effectively control scope without understanding the temporal constraints in which that scope must be delivered.
B. Organizational process assets updates: This is an output of the Control Scope process. After the process is performed, any new procedures or " lessons learned " regarding scope control are used to update the organization ' s assets.
C. Project document updates: This is a common output of almost all monitoring and controlling processes. As variances are found or changes are approved, documents like the Requirements Traceability Matrix or the Stakeholder Register may need to be updated.
D. Work performance information: This is an output of the Control Scope process. The input is Work Performance Data (raw observations). Once that data is compared against the scope baseline, it becomes " information " (e.g., " The project is currently 10% over-scoped " ).
The primary inputs defined by PMI for this process are:
Project Management Plan: Including the Scope Management Plan, Requirements Management Plan, Change Management Plan, Configuration Management Plan, Scope Baseline, and Schedule Baseline.
Project Documents: Such as Lessons Learned Register, Requirements Documentation, and the Requirements Traceability Matrix.
Work Performance Data: Raw data on which deliverables have been started, their progress, and which have been finished.
Organizational Process Assets: Policies and procedures for scope control.