Chap 5.6 Control Scope

Chapter 5 –
Project Scope Management
Control Scope
PMP
Trainer: Anand BobadePMBOK 6th Edition, 2019, All rights reserved.
SIXTH EDITION

PMBOK 6 - All rights reserved 2019, By: Anand Bobade (nmbobade@gmail.com)
5.6 Control Scope
Process overview
Scope creep
Control scope Process Definition
Control scope - ITTO
What is variance analysis?
What is Trend analysis?
Review

Scope Management processes
Plan scope
management
Collect
Requirements
Define Scope
Create WBS Validate Scope Control Scope
P P P
MC MCP

Control Scope -> Overview
Monitor &
Control
Project work
Avoid scope
creep
Perform
Integrated
change
control

Change is inevitable; therefore some type of change
control process is mandatory for every project
Controlling project scope ensures all requested changes
& recommended corrective or preventive actions are
processed through the Perform Integrated Change
Control process
Control Scope is also used to manage the actual changes
when they occur and is integrated with the other control
processes.
Control Scope -> Overview

The uncontrolled expansion to product or project scope
without adjustments to time, cost, and resources is referred
as SCOPE CREEP.
Poorly
defined
requirement
s
Lack of
stakeholder
engagement
Not
managing
scope
baselines
Poor Change
control process
Control Scope -> Scope creep

Monitoring the status of the project and product
scope and managing changes to the scope baseline
It allows the scope baseline to be maintained throughout
the project.
Control Scope process definition
Monitoring
status of Project
Monitor
product
scope
Manage
changes to
scope baseline

Data Analysis
Project Management
plan
Project Documents
Work Performance
Data
Organizational process
assets
Work Performance
Information
Change Request
PMP Updates
Project Documents
updates
Inputs Tools & Techniques Outputs
Control Scope Process ->ITTO

Project Management
plan
Project Documents
Work Performance
Data
Organizational
process assets
Control Scope -> Input

Project
Management plan
Following subsidiary plans & baseline will provide key input:
Control Scope -> Input -> Project Management plan
Scope Management plan
Requirements
Management plan
Scope baseline
Change Management plan
Configuration Management
plan
Performance measurement
baseline

Project Documents
Following Project Documents will provide key input:
Control Scope -> Input -> Project Documents
Requirements
Documentation
Req. Traceability
Matrix
Lessons Learned
Register

Work Performance
Data
The scope completed or No of deliverables produced, in the last
reporting period goes into the work performance data.
Following WPD can be obtained from Change log:
No of Change request received No of request accepted
Control Scope -> Input -> Work Performance Data

Organizational
process assets
The OPAs that can influence control scope process include
Control Scope -> Input -> Organizational process assets
Policies, Procedures
& guidelines
Monitoring & reporting
templates

Data Analysis
Control Scope -> Tools & Techniques

Data Analysis
The two data analysis techniques are:
Control Scope -> T & T -> Data Analysis
Variance analysis Trend analysis

Data Analysis
Variance analysis:
• Performance measurement
• Determine cause & degree of difference between baseline & actual
performance.
• Helps deciding whether corrective or preventive action is required.
Control Scope -> T & T -> Data Analysis -> Variance analysis
- No. of deliverables
completed
- Completed scope
- Completed
activities/work
packages
- Plans
- Scope
- WBS
- PMP - Schedule

Data Analysis
Trend analysis:
• Comparison current performance with performance
measurement baseline though Earned Value Analysis.
Determine, if performance is improving or
deteriorating
Examines project performance over time
(EVM)
Control Scope -> T & T -> Data Analysis -> Trend analysis

Control Scope -> Outputs
Work Performance
Information
Change Request PMP Updates
Project Documents
updates

Work Performance
Information
How the project scope is performing compared to scope baseline.
How they impact schedule & cost, forecast future scope performance.
Control Scope -> Outputs -> Work Performance Information

Change Request
Change request will be raised to:
fix project scope to fit the plan Change plan to fit the project scope
Present Nonconformities Corrective action
Future Nonconformities Preventive action
Past Nonconformities Defect repair
Corrective
action
Preventive
action
Defect repair
Control Scope -> Outputs -> Change Request

Change Request
Control Scope -> Outputs -> Change Request
Corrective action:
•Variance is corrected and the project scope can
continue as planned.
• E.g., add temporary resource to recover from
delay.
Preventive action:
•Potential variance in the future is prevented by
reversing trend in the performance baseline.
•E.g., add resource to ensure timely completion of
work to avoid future delay.
Defect repair:
•Variance is repaired and project scope can
continue as planned.
•E.g., Additional test cycle to ensure all defects are
fixed & tested.

PMP Updates
Following PMP components may get updated.
Control Scope -> Outputs -> PMP Updates
Scope Management
plan
Scope Baseline Schedule Baseline
Cost Baseline
Performance
measurement
baselines

Project Documents
updates
Control Scope -> Outputs -> Project Documents updates
Following Project Documents may get updated.
Lessons Learned
Register
Requirements
documentation
Requirements
Traceability Matrix

Control Scope -> Review
Process overview
Scope creep
Control scope Process Definition
Control scope - ITTO
What is variance analysis?
What is Trend analysis?
Review

Chap 5.6 Control Scope

More Related Content

What's hot

Similar to Chap 5.6 Control Scope

More from Anand Bobade

Chap 5.6 Control Scope