Control scope Subject: Project management Instructor: Mr. Tahir SakhiBy: Nooria Esmaelzade7/30/ 2016

Here is the Scope Management Processes, but we will cover only the control scope

Initiation Planning Executing Controlling

5.1 Collect Requireme

nts

5.2 Define Scope

5.3 Create WBS

5.4 Verify Scope

5.5 Control Scope

A short definition of scope

Scope refers to the detailed set of deliverables or features of a project. These deliverables are derived from a project’s requirements.

Why we need to control the scope?

To monitor the status of the project, finding whether the deliverables meet documented requirements, and managing changes to project scope baseline. Otherwise we will not get the expected result as we planed.

What we need to control the scope and why?

Inputs

1. Project Management Plan

2. Requirements documentation

3. Requirements traceability

4. Work performance data

5. Organizational process assets

1- First thing to look at is the project management plan

Why project management plan?

Because it contains the scope baseline, which is the ‘expected scope’ against which

implemented scope of the project is compared and variance is calculated. If there is a

deviation then project manager needs to plan corrective or preventive actions by running

change request through change control board.

Other information we use from project

management plan are:

- requirements management plan

- scope management plan

- change management plan and

- configuration management plan

which help in Control Scope process.

2- requirements documentation and requirement traceability matrix 

Why?? To verify whether deliverables indeed satisfy the

documented requirements or there are any deviations.

3- Work Performance Data

Why? Because we need to know how are we doing on the

project execution, which is the performance related data, such as how many deliverables have started, what stages of development they are at, how many change requests are received and which deliverables are completed.

4-organizational Process assets

Why?Because they are the policies, procedures, templates and guidelines set by the organization to control scope, as well as any templates already available will help us control scope better.

How do you control scope?

Tools & techniques Variance analysis

Why we need to do Variance analysis?

Variance analysis is the quantitative investigation of the difference between actual and planned behavior.

By comparing project’s current state of scope against the baselined scope information, and finding differences. If and when a variation is found, a corrective or preventive action is identified. 

What is the control scope outputs and why we need to provide them?

Outputs

1. Work performance information

2. Change request 3. Project management plan 4. Project documents updates 5. Organizational process

assets

Work performance information

Why? It is the ‘as of now’ status of the processes from each knowledge

area. It refers to what work has been completed, or how much time has been elapsed, or the cost incurred, etc. It provides us information about the current status of the project deliverables. This information is utilized in the creation of the work performance measurements and the performance reporting.

change requests

Why ? Maybe you or customer will find lot of things incorrect

and such complaints are document and ran through change control board. These are generated to implement corrective or preventive actions taken to manage scope variance. These could also be due to changes requested by customer.

Update plans and documents

Why? If after controlling the change impact is huge then we

may even end up making updates to project documents such as requirements documents and requirement traceability matrix.

Subsidiary management plans such as scope management plan as the project management activity itself provides feedback on how we’d planned to do it earlier. So you update project management plan with this information.

Thank you

“We need to control everything to succeed”