1. 5.5 Control Scope
The process of monitoring the status of both the project and product scope
Focuses on managing any changes to the scope baseline and understanding the flow on impacts to Time, Cost and Quality
All requested changes should be processed through the Perform Integrated Change Control process (4.5)
Occurs during the Monitoring and Control activities through both the Planning and Execution Phases
Scope creep occurs when
unapproved changes are undertaken
Initiation
Planning
Execution
Close
Monitor
Control
Adapted from PMBOK 4th Edition

2. 5.5 Control Scope Change on projects is inevitable
Sometimes requirements and deliverables are overlooked during planning
Sometimes requirements need to change to accommodate the changing needs of the Project Sponsor or customer
Mandating some form of change control process is critical to project success
Initiation
Planning
Execution
Close
Monitor
Control
Adapted from PMBOK 4th Edition

3. 5.5 Control Scope The goals of Change Control are to -
Influence the factors that cause scope changes
Ensure changes are processed according to procedures developed as part of integrated change control
Manage changes when they occur
Increase the chance of meeting the overall objectives
Define and obtain approval for changes to baselines for Scope, Cost and Time
The Project Manager has the primary
responsibility for Change Control
Initiation
Planning
Execution
Close
Monitor
Control
Adapted from PMBOK 4th Edition

4. 5.5 Control Scope The primary inputs include –
Scope baseline
Scope management plan
Change management plan and procedures
Configuration management plan (if developed)
Requirements management plan (if developed)
The primary outputs include –
Updates to Scope baseline
Updates to other baselines – Time and Cost
Project document update
Change requests
Initiation
Planning
Execution
Close
Monitor
Control
Adapted from PMBOK 4th Edition