Define Scope

Sensei Short Scroll 6 Planning Process Group

Define Scope

Introduction: Why This Matters

Requirements describe what stakeholders need. Scope defines what the project will actually deliver. The Define Scope process transforms collected requirements into a clear, detailed description of the project and product. It establishes the boundaries of the project, clarifies inclusions and exclusions, and creates the foundation for the scope baseline.

On the PMP exam, many scenario questions test whether you can distinguish between requirements documentation and the project scope statement. In practice, clear scope definition prevents disputes, controls stakeholder expectations, and ensures that project success is measured consistently (Project Management Institute, 2021).

Purpose and Objectives

Primary Purpose: To develop a detailed description of the project and its deliverables (Project Management Institute, 2021).

Key Objectives:

  • Document project inclusions and exclusions.
  • Establish acceptance criteria for deliverables.
  • Create a common understanding of what “done” looks like.
  • Provide input for creating the Work Breakdown Structure (WBS).
  • Produce the project scope statement, which becomes part of the scope baseline.

Overview

Define Scope sits between Collect Requirements and Create WBS. It takes the detailed requirements and shapes them into a high level, agreed view of what the project will and will not deliver.

  • Boundary setting: Converts broad requirements into specific inclusions, exclusions, and acceptance criteria.
  • Baseline preparation: Produces the project scope statement that will later combine with schedule and cost to form the performance baseline.

Inputs, Tools and Techniques, Outputs (ITTOs)

Inputs

  • Scope management plan.
  • Project charter.
  • Requirements documentation.
  • Organizational process assets.

Tools and Techniques

  • Expert judgment (experienced project managers and subject matter experts).
  • Product analysis (breaking down deliverables into features and functions).
  • Alternatives generation (exploring options to meet requirements).
  • Decision making (multi criteria analysis, prioritization techniques).
  • Facilitation workshops (scope definition sessions with stakeholders).

Outputs

  • Project scope statement.
  • Project document updates (assumptions log, requirements documentation, stakeholder register).

Project Scope Statement

The project scope statement is the primary output of Define Scope. It describes what the project will deliver and what is excluded.

Typical contents:

  • Product scope description: Characteristics, features, and functions of deliverables.
  • Deliverables: Tangible and verifiable outcomes of the project.
  • Acceptance criteria: Conditions for deliverable approval.
  • Project exclusions: Explicit boundaries to prevent scope creep.
  • Assumptions and constraints: Factors that influence scope definition.

Characteristics

  • Translational: Transforms stakeholder language into a precise, project ready scope description.
  • Clarifying: Makes explicit what is included, what is excluded, and how deliverables will be accepted.
  • Foundational: Serves as the direct input to Create WBS and later planning for schedule and cost.
  • Collaborative: Uses workshops, analysis, and decision making with stakeholders and experts.

Practical Example

Context: Hospital Renovation Project.

Scope statement highlights:

  • Product scope: Renovate 10 operating rooms, upgrade equipment, and install new air filtration systems.
  • Deliverables: Refurbished operating rooms, upgraded surgical equipment, staff training, and updated maintenance manuals.
  • Acceptance criteria: Rooms must meet regulatory standards for sterile environments, and equipment must pass safety certification.
  • Exclusions: Hospital cafeteria and patient waiting areas are not included in scope.
  • Constraints: Work must be completed within 12 months and remain within a 15 million dollar budget.

Outcome: Clear scope prevents stakeholders from requesting unrelated improvements, such as cafeteria upgrades, during execution.

Common Pitfalls

Confusing requirements and scope

  • Pitfall: Treating stakeholder requests as final scope without refinement.
  • Prevention: Use Define Scope to transform requirements into a formal scope statement that has been reviewed and agreed.

Not documenting exclusions

  • Pitfall: Stakeholders assume items are included when they are not.
  • Prevention: Explicitly list what is out of scope in the scope statement.

Vague acceptance criteria

  • Pitfall: Disagreements at project closeout about what “done” means.
  • Prevention: Define measurable and testable acceptance conditions.

Too much detail too early

  • Pitfall: Overcomplicating the scope statement with WBS level detail.
  • Prevention: Keep the scope statement high level but precise. The WBS provides the detailed breakdown next.

Sensei Tip : Think of the scope statement as the fence around the project. It protects the team from unplanned work while making sure stakeholders are clear on what is inside.

Exam Alert : If stakeholders argue about whether something is part of the project, the best place to look is usually the project scope statement, not the WBS or charter. The scope statement is your boundary document.

Exam Lens

Patterns on the PMP Exam:

  • If asked which document defines inclusions, exclusions, deliverables, and acceptance criteria, the answer is the project scope statement.
  • Scope creep scenarios often test whether exclusions and acceptance criteria were properly documented in the scope statement.
  • If asked what comes after requirements documentation, the next step is to Define Scope, not yet to create the WBS.

Sample Question

Question: Stakeholders disagree on whether a training program should be included in a new software implementation. Where should the project manager look for clarity?

  1. Requirements documentation.
  2. Project charter.
  3. Project scope statement.
  4. Work Breakdown Structure.

Correct Answer: C. The project scope statement defines what is included and excluded.

Quick Recap Table

Element Why It Matters Exam Watch Point
Project scope statement Defines inclusions, exclusions, and key deliverables. Primary output of Define Scope.
Acceptance criteria Sets measurable standards for deliverable approval. Exam questions test how deliverables are validated.
Exclusions Prevent uncontrolled scope expansion. Look for scenarios where “not in scope” is the key.
Assumptions and constraints Provide context and limits for scope boundaries. Often appear in situational questions that ask “what should the project manager consider”.

Key Takeaways

  • Define Scope transforms requirements into a formal, agreed project scope statement.
  • The scope statement documents inclusions, exclusions, deliverables, assumptions, constraints, and acceptance criteria.
  • Explicit exclusions and clear acceptance criteria prevent disputes and scope creep.
  • On the PMP exam, scope related situational questions often hinge on whether a scope statement exists and was used.

Next Step

With scope defined, the next process is Create Work Breakdown Structure (WBS). This decomposes the scope statement into manageable components and creates the foundation for scheduling, costing, and resource planning.

Bibliography

Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (7th ed.). Project Management Institute.

Scroll to Top