Define Scope: Inputs, Tools & Techniques, and Outputs

PMBOK v8 Definition

Define Scope is the process of developing a detailed description of the project and product. It occurs within the Planning Process Group and belongs to the Project Scope Management Knowledge Area. The key outputs include the project scope statement, requirements documentation, and other project documents. This process establishes the foundation for the scope baseline by creating a clear, shared understanding of project deliverables and boundaries.

Why It Matters for the Exam

Define Scope is heavily tested on the PMI exam because it directly connects to the scope baseline (project scope statement + WBS + WBS dictionary). Questions frequently appear in situational scenarios where you must identify which document contains specific project boundaries, deliverables, or exclusions. The exam tests your ability to distinguish between the outputs of Define Scope versus other planning processes.

Key Points to Remember (for the exam)

• Main Inputs: Project charter, project management plan (scope management plan), requirements documentation, enterprise environmental factors, organizational process assets
• Main Outputs: Project scope statement, requirements documentation (updated), project documents updates
• Key Tools & Techniques: Expert judgment, decision-making, data analysis, decomposition, interpersonal and team skills (facilitation), product analysis
• Critical Output Detail: The project scope statement includes the description of project scope, major deliverables, and exclusions
• Common Confusion: Do NOT confuse the project scope statement (Define Scope output) with the scope baseline (which includes the scope statement + WBS + WBS dictionary)
• Exam Favorite: "Exclusions" in the scope statement are frequently tested—they clarify what is NOT included in the project
• Decomposition Tool: Decomposition is used here to break deliverables into smaller components, but the WBS itself is created in the Create WBS process, not Define Scope

Typical PMI Exam Example

Situation: A project manager is developing the project scope statement. The sponsor asks for clarification about whether a specific feature is included in the project. Which section of the project scope statement should the project manager reference?

Answer: The exclusions section of the project scope statement defines what is explicitly not part of the project scope.

PMI Exam Traps

• Trap: Confusing "Define Scope" with "Create WBS"

  • Reality: Define Scope produces the project scope statement; Create WBS produces the WBS and WBS dictionary. Both together form the scope baseline.

• Trap: Thinking the scope baseline is a single document

  • Reality: The scope baseline is the approved version of three components: project scope statement, WBS, and WBS dictionary.

• Trap: Assuming "requirements documentation" is the same as the "project scope statement"

  • Reality: Requirements documentation captures stakeholder needs and conditions; the project scope statement describes deliverables, boundaries, and exclusions. They are separate outputs.

• Trap: Forgetting that "product analysis" is a tool used in Define Scope

  • Reality: Product analysis (including techniques like product breakdown, systems engineering, value analysis) is specifically listed as a tool for this process.

Important PMI Connections

Quick Review Questions

1. Which three documents together constitute the scope baseline in predictive environments?

2. What is the purpose of the "exclusions" section in the project scope statement?

3. Name three tools and techniques used in the Define Scope process.

4. What is the key difference between the project scope statement and requirements documentation?

5. In a predictive project, what is the purpose of the WBS according to PMBOK v8?

PMBOK v8 Reference

Section 2.2.2.4 – Develop Scope Structure (Figure 2-16: Define Scope Inputs, Tools and Techniques, and Outputs)