Control Scope is part of the “Scope Management” Knowledge Area, and is part of the “Monitoring and Controlling” Process Group.
Control Scope is the process of monitoring the status of the project and product scope and managing changes to the scope baseline. The key benefit of this process is that it allows the scope baseline to be maintained throughout the project.
Controlling the project scope ensures all requested changes and recommended corrective or preventive actions are processed through the Perform Integrated Change Control process (see Section 4.5). Control Scope is also used to manage the actual changes when they occur and is integrated with the other control processes. The uncontrolled expansion to product or project scope without adjustments to time, cost, and resources is referred to as scope creep. Change is inevitable; therefore some type of change control process is mandatory for every project.
This definition was found in the PMBOK V5
Go back to the Glossary or to the Mapping
[/three_fourth]
[one_fourth_last]
Control Scope has:
Inputs:
- Organizational Process Assets
- Project Management Plan
- Requirements documentation
- Requirements Traceability Matrix
- Work performance data
Outputs:
- Change requests
- Organizational Process Assets updates
- Project documents updates
- Project Management Plan updates
- Work performance information
Tools and techniques:
- Variance analysis
[/one_fourth_last]