Scope Management 5.5 Control Scope:

Quick Link for Scope Management Process 

5.1 Collect requirement

5.2 Define scope

5.3 Create WBS ( Work Breakdown Structure)

5.4 Verify scope

5.5 Control scope

5.5 Control Scope:

This process monitors the status of project and product scope and also manages any changes to the scope baseline. This process uses integrated change control to deal with all requested changes and recommended corrective or preventive actions. As described in the integrated change control process, scope change control is concerned with:

• Assuring that requested changes and recommended corrective or preventive actions are processed through integrated change control (uncontrolled changes are known as "scope creep").

• Managing changes when they occur (following established processes).
• Changes must be evaluated and never automatically accepted or rejected.

Control Scope
Inputs	Tools	Outputs
1.      Project management plan 2.      Work performance information 3.      Requirements documentation 4.      Requirements traceability matrix 5.      Organizational Process Assets	Variance analysis	1.      Work performance  measurements 2.      OPA updates 3.      Change requests 4.      Project management plan updates 5.      Project document updates

Five Key inputs for Control scope

1. Project Management Plan: The scope baseline is the object being controlled and it consists of the scope statement, WBS, and WBS dictionary. Other relevant portions of the project management plan include the change management plan, the configuration management plan, and the requirements management plan.

1. Work Performance information: WPI provides the actual status of the work so that a variance can be calculated for performance reports.

2. Requirements documentation:

3. Requirements Traceability matrix:

4. Organization process assets: Organization process assets that may affect scope control include:

• Existing formal and information procedures for scope control
• Monitoring and reporting methods.

One key tool for control scope:

1.      Variance analysis: used to assess the magnitude of variations from the planned scope baseline and decide whether corrective action is necessary.

Five key outputs for control scope:

1. Work performance measurements: Documenting and communicating planned verses actual performance outcomes (technical and scope). This information is shared with appropriate stakeholders.

2. Organization process assets updates: the historical database should be updated with the causes of variance that have occurs, the corrective action employed and other lessons learned associated with scope change control.

3. Changes Request: If change requires occur during scope control activities, they should be processed using integrated change control. Change requests may occur in variance forms (oral, written, external, internal, legally mandated or optional) and may either expand or reduce the scope of the project.

Change request are often the results of:

• An external event (change in a regulation)
• An error in define the scope (omitted a required featured feature of the product or omitted request tasks)
• A value-adding change (a way is found to do something better, faster or cheaper; for example, new technology becomes available). Value analysis or engineering are common examples.

4. Project management plan updates: Approved changes may affect the project triple constraint and accordingly, according, the scope, cost and schedule baselines should be updated as required.

5. Project document updates: Specific documents that may require updating because of scope changes include requirements documentation and the requirements traceability matrix.