---
ref_id: PR33
ref_type: Process
ref_name: "Control Scope"
version: "1.0.0"
status: Active
pmbok8_source: "PMBOK8 Guide §2.1"
companion_ref_shortcode: PG-APG
related_skills:
  - SKL-05-03
related_artifacts:
  - A08
  - A17
file_path: "reference/processes/PR33-control-scope.md"
---
# PR33 — Control Scope

## Process Identity
| Field | Value |
|---|---|
| **Process ID** | PR33 |
| **Process Name** | Control Scope |
| **Process Group** | Monitoring and Controlling |
| **Knowledge Area** | Scope Management |
| **PMBOK Source** | Process Groups: A Practice Guide §7.4 |

---

## Purpose
Monitor the status of the project and product scope and manage changes to the scope baseline. Ensures the scope baseline is maintained throughout the project.

---

## Inputs
| Input | Description |
|---|---|
| Project management plan | Scope management plan, requirements management plan, change management plan, configuration management plan, scope baseline, performance measurement baseline |
| Project documents | Lessons learned register, requirements documentation, requirements traceability matrix |
| Work performance data | Raw data on scope delivery |
| Organizational process assets | Scope control procedures |

---

## Tools and Techniques
| Tool / Technique | Notes |
|---|---|
| Data analysis | Variance analysis, trend analysis |

---

## Outputs
| Output | Description |
|---|---|
| Work performance information | Processed scope performance data |
| Change requests | Requests for corrective/preventive action or scope baseline changes |
| Project management plan updates | Scope baseline, schedule baseline, cost baseline, performance measurement baseline |
| Project documents updates | Lessons learned register, requirements documentation, requirements traceability matrix |

---

## Key Concepts
- Prevents **scope creep**: uncontrolled expansion of scope without adjustments to time, cost, and resources.
- All change requests go through Perform Integrated Change Control (PR31).
- Change is inevitable; a change control process is mandatory for every project.
- Integrated with all other control processes.

---

## PMBOK 8 Alignment
- Scope control is addressed in the **Scope** performance domain (§2.2).
- Scope baseline changes require the **Assess and Implement Changes** process.

---

## Related Processes
- Feeds into: PR31 (Perform Integrated Change Control)
- Cross-links: PR34 (Control Schedule), PR35 (Control Costs)

---

## Cross-References

| Related Item | Type | Relationship |
|---|---|---|
| A08 | Artifact | Primary artifact produced or updated by this process |
| A17 | Artifact | Primary artifact produced or updated by this process |
| SKL-05-03 | Skill | Skill that executes this process |

## Practitioner Notes

Practitioners executing this process should seek answers to the following questions:
1. Is scope creep monitored against the approved scope baseline?
2. Are variance thresholds defined for triggering corrective action?
3. Are scope changes processed through integrated change control?
4. Is the WBS updated to reflect approved scope changes?
5. Are requirements traceability records updated after scope changes?

## Change Log

| Version | Date | Description | Author |
|---|---|---|---|
| 1.0.1 | 2026-06-03 | Added Cross-References, Practitioner Notes, and Change Log sections (F-12 Batch 4) | PMO Director |
