Guide for Control Scope in Scope Management as per PMBOK Guide Seventh Edition

Control Scope refers to the process of monitoring the status of the project and product scope and managing changes to the scope baseline. The key benefits of this process are that it allows the scope baseline to be maintained throughout the project.

Why is Control Scope important?
Control Scope is important because it prevents the project from deviating from planned scope. Without proper control, the project may experience scope creep, which can lead to increased costs and delayed schedules.

What is Control Scope?
It involves monitoring the status of the scope, managing changes to the scope baseline and ensuring that all requested changes and recommended corrective actions are processed through the project's integrated change control procedures. The inputs, tools and techniques, and outputs of control scope process are part of the process.

How does it work?
The Project Manager uses tools such as a Variance Analysis to compare the planned scope against what was actually delivered. If variances are found, corrective actions may be taken. It may also involve updating the project's scope baseline or other components of the project management plan.

Exam Tips: Answering Questions on Control Scope
To answer questions on Control Scope, focus on understanding the process thoroughly, how to carry it out, and its importance. Remember, strict change control procedures are required for any changes to project or product scope. It's also important to recognize that control scope involves monitoring and controlling the project and the product. The product scope is measured against the product requirements.

Remember the PMBOK Guide's emphasis on integrated change control processes, and any recommended changes or corrective action from the control scope process will have to be reviewed and approved by the change control board.