---
reference_type: Performance Domain
reference_id: PD8-02
name: Scope
version: "1.0.0"
status: Active
edition: PMBOK8
pmbok8_source: "PMBOK8 Guide §2.2 — Scope Performance Domain"
authority: PMI-derived
file_path: "reference/performance-domains/PD8-02-scope.md"
last_updated: "2026-06-07"
---

# PD8-02 — Scope Performance Domain
**Type:** Performance Domain  
**Edition:** PMBOK 8th Edition (2025)  
**PMBOK 8 Source:** PMBOK8 Guide §2.2 — Scope Performance Domain  
**Version:** 1.0.0  

## Definition
The **Scope Performance Domain** addresses the definition, management, and control of the project scope, which is essential as the value of a project derives from the outcome delivered in alignment with its scope (PMBOK8 §2.2). It focuses on eliciting requirements, defining scope boundaries, breaking down work structure, and validating deliverables to prevent scope creep and ensure stakeholder satisfaction.

## Desired Outcomes
Per PMBOK8 §2.2, effective execution of the Scope Performance Domain results in:
- **A clear, shared understanding** of the project and product scope among stakeholders and team members.
- **Systematic identification and management** of requirements, ensuring stakeholder needs are met.
- **Well-defined scope boundaries** that prevent unauthorized changes and control scope creep.
- **A decomposition of work (scope structure)** that provides a clear basis for planning and execution.
- **Formal acceptance and validation** of completed deliverables by relevant stakeholders.

## Key Processes and Activities
This domain encompasses the following 6 canonical processes (PMBOK8 §2.2.2):
1. **Plan Scope Management** (§2.2.2.1) — Documents how the project and product scope will be defined, validated, and controlled.
2. **Elicit and Analyze Requirements** (§2.2.2.2) — Determines, documents, and manages stakeholder needs and requirements.
3. **Define Scope** (§2.2.2.3) — Develops a detailed description of the project and product.
4. **Develop Scope Structure** (§2.2.2.4) — Subdivides project deliverables and work into smaller, more manageable components (e.g., Work Breakdown Structure - WBS, or product backlog).
5. **Monitor and Control Scope** (§2.2.2.5) — Monitors the status of the project and product scope and manages changes to the scope baseline.
6. **Validate Scope** (§2.2.2.6) — Formalizes acceptance of the completed project deliverables.

## Relationship to Principles
| Principle | Connection |
|---|---|
| P8-01 — Holistic View | Scope definition must consider product lifecycle context, integration points, and second-order impacts (§3.3.3). |
| P8-02 — Focus on Value | Scope should be defined to maximize value and outcomes rather than simply delivering a high volume of outputs (§2.2, §3.4.3). |
| P8-03 — Embed Quality | Quality criteria (DoD and acceptance criteria) are integral attributes of scope, preventing defects and rework (§3.5.3). |

## Artifact Connections
| Artifact | Connection |
|---|---|
| A08 — Scope and Requirements Backlog | Documents requirements, user stories, scope statement, and WBS. |
| A13 — Requirements Traceability Matrix | Traces requirements from their origin to deliverables and test cases. |
| A17 — Performance Reporting Record | Tracks scope progress, variances, and completion metrics. |

## Skill Connections
| Skill ID | Skill Name | Connection |
|---|---|---|
| SKL-03-01 | Define Project Scope and WBS | Systematically defines scope boundaries and decomposes work into WBS or backlogs. |
| SKL-03-04 | Elicit and Manage Requirements | Facilitates stakeholder workshops to elicit, analyze, and document requirements. |
| SKL-05-03 | Validate and Control Scope | Manages deliverable reviews, stakeholder sign-offs, and changes to scope baselines. |

## Questions to Ask in Practice
1. Are the boundaries of what is in-scope and out-of-scope explicitly documented and agreed upon?
2. How are we ensuring that every requirements item directly supports a target outcome in the Business Case?
3. What is our definition of done (DoD) for deliverables, and is it consistently understood by the team?
4. Are completed deliverables being validated progressively with the customer to ensure early feedback?

*Authority: PMBOK8 Guide §2.2 — Scope Performance Domain · Source type: PMI-derived*
*Repository: https://github.com/fakhruldeen/PMOSkills*
