According to the PMBOK® Guide, Control Scope is the process of monitoring the status of the project and product scope and managing changes to the scope baseline.
Change Requests: This is a primary output of the Control Scope process. When the actual scope performance deviates from the scope baseline (detected via variance analysis), change requests are generated. These may include preventive or corrective actions, defect repairs, or enhancement requests, and they are processed for review and disposition through the Perform Integrated Change Control process.
Other Key Outputs:
Work performance information.
Project management plan updates (specifically scope baseline and other baseline updates).
Project documents updates.
Analysis of Other Options:
B. Variance analysis: This is a tool and technique used within the Control Scope process to determine the cause and degree of difference between the baseline and actual performance; it is not an output.
C. Accepted deliverables: This is the primary output of the Validate Scope (formerly Verify Scope) process, where the customer formally signs off on completed deliverables.
D. Requirements documentation: This is a key input to the Control Scope process, used as a reference to ensure that all defined requirements are being met and no " gold plating " is occurring.
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit