ExamFinch.com My Study

Study guide

4.3 Planning & Managing Scope

Practice this exam

Project Management Professional PMP

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Introduction & Fundamentals

1.1 About the PMP Exam 1.2 What is a Project? 1.3 Project, Program & Portfolio Management 1.4 The Project Manager Role 1.5 PMBOK 7 Principles Overview 1.6 Performance Domains Overview 1.7 What Changed in the July 2026 PMP Exam

2 Chapter 2: People Domain Part 1

2.1 Managing Conflict 2.2 Leading a Team 2.3 Supporting Team Performance 2.4 Empowering Team Members 2.5 Training & Development 2.6 Building a Team 2.7 Removing Impediments

3 Chapter 3: People Domain Part 2

3.1 Negotiating Project Agreements 3.2 Collaborating with Stakeholders 3.3 Building Shared Understanding 3.4 Engaging Virtual Teams 3.5 Defining Team Ground Rules 3.6 Mentoring Stakeholders 3.7 Emotional Intelligence

4 Chapter 4: Process Domain - Planning

4.1 Determining Project Methodology 4.2 Integrating Project Planning 4.3 Planning & Managing Scope 4.4 Planning & Managing Schedule 4.5 Planning & Managing Budget 4.6 Planning & Managing Quality 4.7 Planning & Managing Resources 4.8 Planning & Managing Procurement

5 Chapter 5: Process Domain - Execution & Control

5.1 Executing with Urgency for Value 5.2 Managing Communications 5.3 Assessing & Managing Risks 5.4 Engaging Stakeholders 5.5 Managing Project Changes 5.6 Establishing Project Governance 5.7 Managing Project Issues 5.8 Managing Project Artifacts 5.9 Knowledge Transfer & Closure

6 Chapter 6: Business Environment Domain

6.1 Planning & Managing Compliance 6.2 Evaluating & Delivering Benefits 6.3 External Environment Changes 6.4 Supporting Organizational Change

7 Chapter 7: Agile & Hybrid Approaches

7.1 Agile Mindset & Values 7.2 Scrum Framework 7.3 Kanban & Lean 7.4 Extreme Programming (XP) 7.5 Hybrid Project Management 7.6 Agile Planning & Estimation 7.7 Agile Metrics & Tools

8 Chapter 8: Predictive (Waterfall) Approaches

8.1 Predictive Lifecycle 8.2 Scope Management 8.3 Schedule Management 8.4 Cost Management 8.5 Quality Management 8.6 Risk Management Process 8.7 Procurement & Contracts 8.8 Change Control

4.3 Planning & Managing Scope

Key Takeaways Explain This Topic AI

The Work Breakdown Structure (WBS) follows the 100% rule, meaning it must capture 100% of the project scope including all deliverables

The scope baseline consists of three components: the project scope statement, the WBS, and the WBS dictionary

Work packages are the lowest level of the WBS for which cost and duration are estimated, typically representing 8-80 hours of work

Requirements gathering techniques include interviews, focus groups, facilitated workshops, questionnaires, prototypes, and observation

Scope validation is the formal acceptance of completed deliverables by the customer, while scope control prevents unauthorized scope changes (scope creep)

Last updated: January 2026

Scope management is about defining and controlling what is and what is not included in the project. It's one of the most critical aspects of project management because scope creep (uncontrolled scope expansion) is a leading cause of project failure.

Scope Management Processes

  • Process Purpose Key Output
  • Plan Scope Management How scope will be defined, validated, and controlled Scope Management Plan
  • Collect Requirements Determine stakeholder needs and expectations Requirements Documentation
  • Define Scope Develop detailed description of project and product Project Scope Statement
  • Create WBS Subdivide deliverables into manageable components WBS and WBS Dictionary
  • Validate Scope Formalize acceptance of completed deliverables Accepted Deliverables
  • Control Scope Monitor scope and manage scope changes Work Performance Information
  • Requirements Gathering

Requirements are the foundation of scope. Poor requirements lead to scope issues throughout the project.

Types of Requirements

  • Type Description Example
  • Business Requirements High-level organizational needs Increase market share by 10%
  • Stakeholder Requirements Needs of individual stakeholders Easy-to-use interface for non-technical users

Solution Requirements Features and functions the product must have System must process 1000 transactions per second

  • Functional Requirements What the product must do User can reset password via email
  • Non-Functional Requirements How the product must perform Page load time under 2 seconds
  • Transition Requirements Needed for transition from current to future state Data migration from legacy system
  • Requirements Gathering Techniques
  • Technique Description Best For
  • Interviews One-on-one conversations with stakeholders Deep understanding, sensitive topics
  • Focus Groups Facilitated group discussions Multiple perspectives, consensus building

Facilitated Workshops Structured sessions with multiple stakeholders Cross-functional requirements, conflict resolution

  • Questionnaires/Surveys Written questions distributed to many people Large audiences, quantitative data
  • Benchmarking Comparing to similar projects or industry standards Best practices, performance targets
  • Prototyping Creating working models for feedback Uncertain requirements, user interface design
  • Observation (Job Shadowing) Watching users perform their work Understanding current processes
  • Document Analysis Reviewing existing documentation Understanding current state, legacy systems
  • Requirements Traceability Matrix (RTM)

The Requirements Traceability Matrix links requirements to their origin and tracks them through the project lifecycle:

  • Req ID Description Source Priority WBS Element Test Case Status
  • REQ-001 User login Stakeholder A High 1.2.1 TC-15 Approved
  • REQ-002 Password reset Stakeholder B Medium 1.2.2 TC-22 In Review
  • REQ-003 Two-factor auth Security Team High 1.2.3 TC-31 Approved
  • Project Scope Statement

The Project Scope Statement provides a detailed description of the project and product scope. It is the basis for making future project decisions.

Key Elements

  • Element Description
  • Product Scope Description Characteristics of the product, service, or result
  • Deliverables Any unique output produced by the project
  • Acceptance Criteria Conditions that must be met for deliverables to be accepted
  • Project Exclusions What is explicitly NOT included in the project
  • Constraints Restrictions that limit project options
  • Assumptions Factors assumed to be true for planning purposes
  • The Work Breakdown Structure (WBS)

The Work Breakdown Structure is a hierarchical decomposition of the total scope of work. It is the most important scope management document and the foundation for planning all other aspects of the project.

WBS Principles

The 100% Rule : The WBS must include 100% of the work defined by the project scope and capture all deliverables. Each level of decomposition represents an increasingly detailed definition of work.

  • WBS Structure Project
  • ├── Phase 1: Planning
  • │ ├── Deliverable 1.1: Project Charter
  • │ │ ├── Work Package 1.1.1: Stakeholder Interviews
  • │ │ └── Work Package 1.1.2: Charter Document
  • │ └── Deliverable 1.2: Requirements Document
  • │ ├── Work Package 1.2.1: Requirements Gathering
  • │ └── Work Package 1.2.2: Requirements Review
  • ├── Phase 2: Design
  • │ ├── Deliverable 2.1: Architecture Document
  • │ └── Deliverable 2.2: UI Designs
  • └── Phase 3: Development
  • ├── Deliverable 3.1: Module A
  • └── Deliverable 3.2: Module B
  • Work Packages

Work packages are the lowest level of the WBS for which cost and duration are estimated:

  • Characteristic Guideline
  • Duration 8-80 hours of work (1-10 days)
  • Responsibility Assigned to a single person or team
  • Measurable Progress can be tracked and measured
  • Independently Schedulable Can be scheduled without breaking down further
  • WBS Types
  • Type Organization Best For
  • Deliverable-Oriented Organized by project deliverables Product development, construction
  • Phase-Oriented Organized by project phases Projects following specific life cycle
  • Organizational Organized by team or department Cross-functional projects
  • WBS Dictionary

The WBS Dictionary provides detailed information about each WBS element:

  • Element Description
  • WBS ID Unique identifier (1.2.3.1)
  • Name Description of the work package
  • Description Detailed definition of the work
  • Responsible Party Who is accountable for completion
  • Milestones Key dates or events
  • Cost Estimate Budget allocated
  • Quality Requirements Standards to be met
  • Acceptance Criteria How completion will be verified
  • References Related documents or dependencies
  • Scope Baseline

The Scope Baseline is the approved version of the project scope and consists of:

  • Project Scope Statement : Detailed description of project and product scope
  • WBS : Hierarchical decomposition of all deliverables
  • WBS Dictionary : Detailed information about each WBS element
  • Why Scope Baseline Matters
  • Provides the reference for all scope-related decisions
  • Changes require formal change control
  • Used to measure project performance
  • Foundation for schedule and cost baselines
  • Scope Validation

Scope Validation is the process of formalizing acceptance of completed project deliverables.

Validation vs. Quality Control

  • Scope Validation Quality Control
  • External focus (customer acceptance) Internal focus (correctness)
  • Concerned with acceptance Concerned with correctness
  • Answers: "Did we build what was requested?" Answers: "Did we build it right?"
  • Validation Activities
  • Inspect Deliverables : Review completed work against requirements
  • Document Acceptance : Formal sign-off from customer/sponsor
  • Document Rejections : Record why deliverables were not accepted
  • Request Changes : Submit change requests for corrections
  • Scope Control

Scope Control monitors the status of the project and product scope and manages changes to the scope baseline.

Scope Creep vs. Gold Plating

  • Issue Definition Cause
  • Scope Creep Uncontrolled expansion of scope Stakeholder requests, poor change control
  • Gold Plating Adding features not in the scope Team adding "nice to have" features
  • Scope Control Activities
  • Monitor scope performance against baseline
  • Evaluate change requests for scope impact
  • Recommend corrective/preventive actions
  • Update project documents as needed
  • Communicate scope status to stakeholders
  • Key Takeaways
  • Requirements are the foundation of scope management
  • The WBS decomposes all deliverables following the 100% rule
  • Work packages are the lowest WBS level for estimating and scheduling
  • The Scope Baseline = Scope Statement + WBS + WBS Dictionary
  • Validate Scope gets formal customer acceptance
  • Control Scope prevents unauthorized changes and scope creep

Loading diagram... Scope Baseline Components