HKSM
Control Scope
The process of systematically tracking the state of both project and product scope and controlling any changes to the approved scope baseline.
Key Points
- Continuously compare actual deliverables and work against the scope baseline (scope statement, WBS, and WBS dictionary).
- Identify and analyze scope variances; submit change requests through Perform Integrated Change Control when needed.
- Prevent scope creep and gold plating by enforcing formal approval for any scope adjustments.
- Typical outputs include work performance information, change requests, and updates to the scope baseline and project documents (e.g., requirements traceability matrix).
Example
Midway through a software project, a stakeholder asks for an extra dashboard not in the approved scope. The project manager documents the request, assesses impact on cost, schedule, and quality, and submits it to change control. After approval, the WBS and scope baseline are updated and communicated to the team; if not approved, the team continues with the original scope and the request is deferred or rejected.
PMP Example Question
During testing, the team discovers a module includes additional features that were not part of the approved scope. What should the project manager do next?
- Accept the extras if they do not affect the budget or schedule.
- Instruct the team to remove unapproved features and submit a change request if stakeholders still want them.
- Update the scope baseline to capture the improvement.
- Fast-track remaining work to accommodate the added features.
Correct Answer: B — Remove unapproved additions and use formal change control
Explanation: Control Scope requires preventing gold plating and managing any scope change through the change control process. Unapproved features should not be kept in the product without formal approval.
