---
ref_id: PR06
ref_type: Process
ref_name: "Define Scope"
version: "1.0.0"
status: Active
pmbok8_source: "PMBOK8 Guide §2.2.2.3"
companion_ref_shortcode: PG-APG-5.4
related_skills:
  - SKL-03-01
  - SKL-03-02
related_artifacts:
  - A04
  - A05
  - A08
  - A13
  - A14
file_path: "reference/processes/PR06-define-scope.md"
---

# PR06 — Define Scope

**Ref ID:** PR06
**Type:** Process
**PMBOK8 Source:** §2.2.2.3
**Version:** 1.0.0

---

## Definition

Define Scope is the process of developing a detailed description of the project and product, including quality requirements and standards for deliverables.

## Key Characteristics

- **Boundary Setting:** Explicitly documents what is included in the project (in-scope) and what is excluded (out-of-scope).
- **Core Specification:** Converts customer requirements and strategic charter goals into a clear, detailed Project Scope Statement.
- **Acceptance Anchoring:** Outlines specific, measurable acceptance criteria and quality standards for major deliverables.
- **Creep Shield:** Serves as the primary reference baseline to prevent unauthorized changes (scope creep).
- **Lifecycle Adaptation:** Produces the comprehensive scope statement in predictive projects, or refines product roadmaps and release boundaries iteratively in adaptive environments.

## PMBOK 8 Context

Under PMBOK 8, Define Scope is situated within the **Scope Performance Domain** and links directly to **Governance**. Setting unambiguous project boundaries is crucial for maintaining change control integrity and ensuring the delivery of expected business value. This process relies on elicitation outputs and directly feeds decomposition activities.

## Inputs

| Input | Description | Source |
|---|---|---|
| Project Charter | Outlines the high-level project boundary, objectives, and early deliverables context. | PR01 Develop Project Charter |
| Project Management Plan | Provides the scope planning rules and selected developmental approach context. | PR03 Develop PMP |
| Requirements Documentation | The compiled and structured list of stakeholder needs to be analyzed and bounded. | PR05 Collect Requirements |
| Project Documents | Assumption logs and context registers containing constraints and structural boundaries. | Project Registry |

## Outputs

| Output | Description | Destination |
|---|---|---|
| Project Scope Statement | A detailed description of the project deliverables, boundaries, and acceptance criteria. | A14 Integrated Project Management Plan |
| Requirements Updates | Refinements or corrections to elicited requirements discovered during boundary definition. | A08 Scope and Requirements Backlog |

## Tools and Techniques

- **Expert Judgment:** Guidance on technical engineering, domain architecture, and scope mapping.
- **Data Analysis:** Alternatives analysis to evaluate different ways of delivering the requested product or service.
- **Decision Making:** Multicriteria decision analysis to prioritize features and reach consensus on boundaries.
- **Decomposition:** Preliminary division of major deliverables to facilitate structured definition.
- **Interpersonal Skills:** Facilitation and active negotiation to resolve differences in stakeholder scope expectations.
- **Product Analysis:** Product breakdown, systems engineering, value engineering, and analysis to define features.

## Cross-References

| Related Item | Type | Relationship |
|---|---|---|
| A04 | Artifact | Source of high-level objectives and business parameters |
| A05 | Artifact | Supplying environmental assumptions and project constraints |
| A08 | Artifact | Backlog refined in adaptive or hybrid projects |
| A13 | Artifact | Mapping scope boundaries back to stakeholder requirements |
| A14 | Artifact | Destination for the Project Scope Statement baseline |
| PR05 | Process | Elicits the stakeholder needs from which scope is defined |
| PR07 | Process | Receives the detailed scope statement for WBS decomposition |
| SKL-03-02 | Skill | Plan Scope and Requirements |

## Practitioner Notes

Practitioners executing this process should seek answers to the following vital questions:
1. Are deliverables described in sufficient detail to guide subsequent WBS decomposition and quality planning?
2. Are explicit, unambiguous exclusions documented to prevent stakeholder misunderstandings regarding project boundaries?
3. How are quality requirements and formal acceptance criteria captured within the scope definition?
4. Does the defined scope fully trace back to and satisfy the strategic objectives of the project charter?
5. In adaptive contexts, is the product roadmap and release-level scope definition detailed enough to support iteration planning?

## 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.3; Process Groups Practice Guide §5.4*
