Plan Scope Management

Sensei Short Scroll 4 Planning Process Group

Plan Scope Management

Introduction: Why This Matters

Scope is the backbone of every project. Without clear boundaries, projects drift into endless changes, overruns, and dissatisfied stakeholders. The Plan Scope Management process defines how scope will be defined, validated, and controlled throughout the project. It sets the rules of engagement for scope decisions and creates alignment among stakeholders before detailed requirements are collected.

On the PMP exam, scope related questions often test whether you know the framework should exist first. You cannot effectively define or control scope without first planning how scope will be managed (Project Management Institute, 2021).

Purpose and Objectives

Primary Purpose: To establish policies, procedures, and documentation that guide the management of project and product scope.

Key Objectives:

  • Clarify how scope will be defined and refined.
  • Define how deliverables will be validated and accepted.
  • Establish processes for preventing and managing scope creep.
  • Document roles and responsibilities for scope related decisions.
  • Produce the Scope Management Plan and the Requirements Management Plan.

Overview

Plan Scope Management creates the framework for all future scope work. It comes before Collect Requirements, Define Scope, and Create WBS, and it answers the question: “How will we manage boundaries and expectations on this project?”

  • Planning focus: Establish structure for defining, validating, and controlling scope.
  • Coverage: Produces two critical plans that guide scope and requirements throughout the life cycle.

Characteristics

  • Input based: Uses the project charter, elements of the project management plan (quality, life cycle, and development approach), enterprise environmental factors, and organizational process assets.
  • Guided by expertise: Relies on expert judgment from the PMO, experienced project managers, and domain experts to shape practical scope rules.
  • Collaborative: Uses data analysis and planning workshops with sponsors, team members, and key stakeholders to align expectations.
  • Output focused: Produces the Scope Management Plan and Requirements Management Plan, which become reference documents for all scope decisions.

ITTO View

Inputs

  • Project charter.
  • Project management plan (quality, life cycle, and development approach sections).
  • Enterprise environmental factors (organizational culture, industry standards).
  • Organizational process assets (templates, policies, historical lessons).

Tools and Techniques

  • Expert judgment (PMO, experienced project managers, domain experts).
  • Data analysis (alternatives analysis for selecting approaches).
  • Meetings (planning workshops with sponsor, team, and stakeholders).

Outputs

  • Scope Management Plan.
  • Requirements Management Plan.

What the Scope Management Plan Includes

The Scope Management Plan outlines the rules of the game for scope on this project.

Typical components:

  • Process for preparing the project scope statement.
  • Process for creating the Work Breakdown Structure (WBS).
  • Process for formal acceptance of completed deliverables.
  • Process for controlling scope changes.
  • Roles and responsibilities for scope decision making.
  • Guidance on how scope related documents will be maintained.

What the Requirements Management Plan Includes

While the Scope Management Plan defines how scope is managed, the Requirements Management Plan defines how requirements are captured and tracked.

Typical components:

  • Process for gathering requirements (interviews, surveys, workshops).
  • Process for analyzing, prioritizing, and documenting requirements.
  • Requirements traceability matrix that links requirements to objectives and deliverables.
  • Process for handling requirement changes.
  • Tools or systems used to manage requirements.

Practical Example

Context: University Online Learning System.

Scope Management Plan highlights:

  • Scope will be defined through collaboration with faculty, IT, and students.
  • A WBS will capture all deliverables, including system configuration, training, and documentation.
  • Deliverables will be validated through user acceptance testing.
  • Scope changes will be managed through a change control board.

Requirements Management Plan highlights:

  • Requirements will be gathered through student surveys, faculty interviews, and vendor workshops.
  • Requirements will be prioritized using a MoSCoW (Must, Should, Could, Will not) technique.
  • A traceability matrix will link requirements to system features, test cases, and project objectives.

Outcome: With these plans in place, the university gains clarity in defining and controlling scope and reduces the likelihood of disputes during execution.

Common Pitfalls

Skipping the Scope Management Plan

  • Pitfall: Teams jump straight into collecting requirements without defining the process.
  • Prevention: Always establish how scope will be managed before collecting details.

Confusing scope and requirements

  • Pitfall: Teams use requirements documentation as the scope baseline.
  • Prevention: Scope defines boundaries. Requirements describe deliverables inside those boundaries.

Weak change control

  • Pitfall: Stakeholders push scope changes informally.
  • Prevention: Require all scope changes to follow the formal change control process.

No traceability

  • Pitfall: Requirements get lost between stakeholder input and final deliverables.
  • Prevention: Use a traceability matrix to track requirements end to end.

Sensei Tip : Remember the difference. The Scope Management Plan governs boundaries and deliverables. The Requirements Management Plan governs the details that define those deliverables.

Exam Alert : If a question shows the sponsor or team jumping straight into collecting requirements or building the WBS, the best first step is usually to develop the Scope Management Plan and Requirements Management Plan, not to start detailed work immediately.

Exam Lens

Patterns on the PMP Exam:

  • If asked what the project manager should do first in scope related questions, the correct answer often involves Plan Scope Management before collecting requirements or defining scope.
  • If asked how to prevent scope creep, look for answers that reference formal acceptance and change control processes defined in the Scope Management Plan.
  • Expect references to the Requirements Traceability Matrix in questions about missed or unclear requirements.

Sample Question

Question: A project manager is beginning work on a new system upgrade. The sponsor wants to collect detailed requirements immediately, but no process exists for scope definition or acceptance. What should the project manager do first?

  1. Begin collecting requirements to satisfy the sponsor.
  2. Develop the Scope Management Plan and Requirements Management Plan.
  3. Create the WBS.
  4. Proceed with execution and refine scope later.

Correct Answer: B. The first step is to define how scope and requirements will be managed before collecting details.

Quick Recap Table

Element Why It Matters Exam Watch Point
Scope Management Plan Defines how project scope will be managed. Needed before collecting requirements.
Requirements Management Plan Defines how requirements will be gathered, analyzed, and tracked. Expect questions involving the requirements traceability matrix.
Acceptance criteria Clarifies how deliverables will be validated and accepted. Exam often tests formal acceptance versus informal approval.
Change control for scope Prevents unmanaged scope creep. Correct answers emphasize controlled, documented changes.

Key Takeaways

  • Plan Scope Management defines how scope is created, validated, and controlled.
  • The Scope Management Plan and Requirements Management Plan are the key outputs of this process.
  • These plans provide guardrails for scope definition and change, which reduces disputes and scope creep.
  • On the PMP exam, scope questions often test whether you recognize the need for these plans before moving forward.

Next Step

With the scope management framework established, we move to the next process: Collect Requirements, where the focus shifts from how to manage requirements to actually gathering them from stakeholders.

Bibliography

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

Scroll to Top