---
ref_id: PR04
ref_type: Process
ref_name: "Plan Scope Management"
version: "1.0.0"
status: Active
pmbok8_source: "PMBOK8 Guide §2.2.2"
companion_ref_shortcode: PG-APG-5.2
related_skills:
  - SKL-03-01
  - SKL-03-02
related_artifacts:
  - A04
  - A05
  - A08
  - A13
  - A14
file_path: "reference/processes/PR04-plan-scope-management.md"
---

# PR04 — Plan Scope Management

**Ref ID:** PR04
**Type:** Process
**PMBOK8 Source:** §2.2.2
**Version:** 1.0.0

---

## Definition

Plan Scope Management is the process of creating a scope management plan that documents how the project and product scope will be defined, validated, and controlled.

## Key Characteristics

- **Governance Groundwork:** Establishes the clear rules of engagement for defining, detailing, and managing scope.
- **Dual Outputs:** Produces both the Scope Management Plan and the Requirements Management Plan as vital PMP components.
- **Life Cycle Tailoring:** Outlines how scope will be managed according to the chosen delivery model (WBS for predictive, Backlog for adaptive).
- **Control Strategy:** Determines how change requests affecting the scope baseline or backlog will be formally requested and evaluated.
- **Traceability Framing:** Sets the requirements for tracing and connecting deliverables directly to stakeholder expectations.

## PMBOK 8 Context

Under PMBOK 8, Plan Scope Management resides in the **Scope Performance Domain** and links directly to project **Governance**. Defining the rules for scope validation and change control prevents scope creep and ensures value is delivered as intended. In adaptive or hybrid projects, scope planning is iterative, with backlog prioritization heuristics established in this process.

## Inputs

| Input | Description | Source |
|---|---|---|
| Project Charter | Supplies the initial strategic context, high-level requirements, and product boundaries. | PR01 Develop Project Charter |
| Project Management Plan | Provides the overarching lifecycle and developmental approach context. | PR03 Develop PMP |
| Enterprise Environmental Factors | Infrastructure, corporate culture, standard practices, and industry regulations. | Enterprise |
| Organizational Process Assets | Templates, historical lessons learned, and institutional policies. | PMO Registry |

## Outputs

| Output | Description | Destination |
|---|---|---|
| Scope Management Plan | Documents how project scope will be defined, developed, monitored, controlled, and validated. | A14 Integrated Project Management Plan |
| Requirements Management Plan | Documents how project and product requirements will be analyzed, documented, and managed. | A14 Integrated Project Management Plan |

## Tools and Techniques

- **Expert Judgment:** Advice on scope strategies, estimation approaches, and software configuration tools.
- **Data Analysis:** Alternatives analysis to evaluate different ways of defining, validating, and controlling scope.
- **Meetings:** Alignment workshops with key stakeholders, business analysts, and core project team leaders.

## Cross-References

| Related Item | Type | Relationship |
|---|---|---|
| A04 | Artifact | Input context providing high-level boundaries and strategic constraints |
| A05 | Artifact | Supplying environmental assumptions and project constraints |
| A08 | Artifact | Backlog governance basis in adaptive or hybrid environments |
| A13 | Artifact | Traceability matrix managed under the requirements management plan guidelines |
| A14 | Artifact | Principal destination for scope and requirements plans |
| PR05 | Process | Downstream requirements collection process governed by this plan |
| SKL-03-02 | Skill | Plan Scope and Requirements |

## Practitioner Notes

Practitioners executing this process should seek answers to the following vital questions:
1. How will scope be defined — through a detailed scope statement and WBS, through a dynamic backlog, or via a hybrid approach?
2. What specific change control procedures will govern modifications to the scope baseline or product backlog?
3. How will requirements be elicited, documented, prioritized, and systematically traced through delivery?
4. How will formal scope validation and deliverable acceptance be performed and by whom?
5. Does the chosen scope planning strategy align with the project's selected development life cycle (predictive, adaptive, or hybrid)?

## Change Log

| Version | Date | Description | Author |
|---|---|---|---|
| 1.0.0 | 2026-06-02 | Rebuilt to align with canonical REF file structure and YAML front-matter | PMO Director |

---

*Authority: PMBOK8 Guide §2.2.2; Process Groups Practice Guide §5.2*
