Plan Scope Management: Creating the Scope Management Plan

PMBOK v8 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. This process belongs to the Scope Management performance domain and is classified as a Planning process. The key benefit of this process is that guidance on scope management is provided to ensure that value is delivered to stakeholders. The scope management plan should be defined, developed, monitored, validated, and controlled based on the project life cycle.

Why It Matters for the Exam

This concept appears frequently in PMI exam questions testing your understanding of planning processes and their outputs. Expect questions that ask you to distinguish between the scope management plan and other planning documents, or that test which components belong in this plan versus the project management plan. Questions often appear in definition-based and process-sequence formats.

Key Points to Remember (for the exam)

• Main Output: Scope management plan (a component of the program or project management plan)
• Core Purpose: Describes how the scope will be defined, developed, monitored, controlled, and validated
• Four Required Components:
  • Process for preparing a project scope statement
  • Process that enables the creation of the work breakdown structure (WBS) from the detailed project scope statement
  • Process that establishes how the scope baseline will be approved and maintained
  • Process that specifies how formal acceptance of the completed project deliverables will be obtained
• Key Distinction: Plan Scope Management defines how scope will be managed, not the scope itself
• Life Cycle Adaptation: The approach differs between adaptive (iterative, collaborative) and predictive projects, though the objective of ensuring value delivery remains the same
• Value Focus: This process eliminates or removes unnecessary work that will not add value to the project
• Related Process: Validate Scope is the process of formalizing acceptance of the completed project deliverables (separate from Plan Scope Management)

Typical PMI Exam Example

A project manager is leading a new software development project. During the planning phase, the team needs to document how they will define project deliverables, create the WBS, handle scope changes, and obtain formal acceptance. Which process is being performed? → Plan Scope Management, producing the scope management plan as the output.

PMI Exam Traps

• Trap: Confusing the scope management plan with the project scope statement

  • Reality: The scope management plan describes how scope is managed; the project scope statement describes what the scope is

• Trap: Thinking the scope management plan includes the actual scope baseline

  • Reality: The scope management plan establishes how the scope baseline will be approved and maintained, but the baseline itself is a separate output from Define Scope and Create WBS

• Trap: Assuming Plan Scope Management is only for predictive projects

  • Reality: Adaptive projects also need scope management guidance, but the approach is more iterative and collaborative

• Trap: Confusing "Validate Scope" with "Control Quality"

  • Reality: Validate Scope is about formal acceptance of completed deliverables; Control Quality is about measuring deliverables against quality standards

Important PMI Connections

Quick Review Questions

1. What are the four components that must be included in a scope management plan?

2. How does the approach to Plan Scope Management differ between adaptive and predictive projects?

3. What is the key benefit of the Plan Scope Management process?

4. Which process formalizes acceptance of completed project deliverables, and how is it related to the scope management plan?

5. True or False: The scope management plan contains the actual scope baseline for the project.

PMBOK v8 Reference

Section 2.2.2.1 – Plan Scope Management (Scope Management performance domain)