8.2 Scope Management

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

Free exam prep PMP Project Management Professional Practice Questions 250 questions Study Guide 57 topics Cheat Sheet 62 facts Flashcards 50 cards

8.2 Scope Management

Key Takeaways Explain This Topic AI

The Project Charter is the formal document that authorizes the project and gives the project manager authority to apply organizational resources

Requirements documentation captures stakeholder needs and expectations, forming the foundation for scope definition

The Scope Statement defines project deliverables, acceptance criteria, exclusions, constraints, and assumptions

The Work Breakdown Structure (WBS) decomposes the total project scope into manageable work packages following the 100% Rule

The Scope Baseline consists of three components: the Scope Statement, the WBS, and the WBS Dictionary Last updated: January 2026

Scope management is the process of ensuring that the project includes all the work required to complete the project successfully — and only that work. In predictive projects, scope is defined upfront and controlled through formal change management throughout the project. The Scope Management Framework Scope management follows a logical progression from high-level authorization through detailed work breakdown:

Process Purpose Key Output Plan Scope Management Define how scope will be managed Scope Management Plan Collect Requirements Capture stakeholder needs Requirements Documentation Define Scope Create detailed scope description Scope Statement Create WBS Decompose scope into work packages WBS and WBS Dictionary Validate Scope Obtain formal acceptance Accepted Deliverables Control Scope Monitor and manage scope changes Work Performance Information The Project Charter The Project Charter is the formal document that authorizes a project and gives the project manager the authority to apply organizational resources to project activities. Key Elements of a Project Charter

Element Description Project Purpose Why the project is being undertaken Measurable Objectives What success looks like High-Level Requirements Major stakeholder needs Summary Milestone Schedule Key dates and deliverables Pre-approved Budget Initial funding authorization Project Manager Authority Level of decision-making power Stakeholder List Key stakeholders and their roles Success Criteria How completion will be measured Charter vs. Contract For external projects, the contract often serves as the project charter. However, the project manager should still create an internal charter to document assumptions and establish authority. Requirements Documentation Requirements documentation captures all project and product requirements gathered from stakeholders. Types of Requirements

Type Description Examples Business Requirements High-level organizational needs Increase market share by 10% Stakeholder Requirements Needs of specific stakeholders Sales team needs mobile access Solution Requirements Functional and non-functional specifications System must process 1,000 transactions/second Transition Requirements Needs for moving to new state Data migration, training Project Requirements Actions or conditions for project Milestones, compliance Requirements Gathering Techniques Interviews — One-on-one discussions with stakeholders Focus Groups — Facilitated sessions with multiple stakeholders Questionnaires — Structured data collection from many people Observations — Watching users perform current processes Prototypes — Creating models to elicit feedback Benchmarking — Comparing to industry standards or best practices Document Analysis — Reviewing existing documentation Requirements Traceability Matrix (RTM) The Requirements Traceability Matrix links requirements throughout the project lifecycle:

Requirement ID Description Source Priority WBS Element Test Case Status REQ-001 User login Stakeholder A High 1.2.1 TC-001 Approved REQ-002 Report generation Business Need Medium 1.3.2 TC-015 In Review The Scope Statement The Project Scope Statement provides a detailed description of the project and product scope, including deliverables and the work required to create them. Key Components of the Scope Statement

Component Description Product Scope Description Features and functions of the product/service Deliverables Measurable outputs the project will produce Acceptance Criteria Conditions that must be met for deliverables to be accepted Project Exclusions What is specifically NOT included in scope Constraints Limitations or restrictions on the project Assumptions Factors believed to be true for planning purposes Scope Exclusions Explicitly stating what is NOT included in scope is as important as defining what is included: Prevents scope creep by establishing clear boundaries Manages stakeholder expectations Documents decisions made during planning Provides reference for change control decisions Work Breakdown Structure (WBS) The Work Breakdown Structure is a hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables. The 100% Rule The 100% Rule is the fundamental principle of WBS construction: The WBS includes 100% of the work defined by the project scope and captures all deliverables — internal, external, and interim — in terms of the work to be completed, including project management. WBS Structure Levels

Level Name Description Level 1 Project The project name or title Level 2 Major Deliverables Main components or phases Level 3 Sub-Deliverables Breakdown of major deliverables Level 4+ Work Packages Lowest level of decomposition Work Package Characteristics A work package is the lowest level of the WBS and should be: Definable — Clear scope and boundaries Assignable — Can be given to a single person or team Estimable — Duration and cost can be estimated Measurable — Progress can be tracked WBS Dictionary The WBS Dictionary provides detailed information about each WBS element:

Field Description WBS ID Unique identifier (e.g., 1.2.3.1) Description What the element includes Assumptions What is assumed true for this element Constraints Limitations on this element Responsible Organization Who owns this work Milestones Key dates associated with this element Resources Required People, equipment, materials needed Quality Requirements Standards that must be met Acceptance Criteria How completion will be verified The Scope Baseline The Scope Baseline is an approved version of the scope that provides the basis for comparison: Components of Scope Baseline Project Scope Statement — Detailed description of project and product scope WBS — Hierarchical decomposition of all project work WBS Dictionary — Detailed information about each WBS element Any changes to the scope baseline require formal change control. Scope Verification and Control Validate Scope Validate Scope is the process of formalizing acceptance of the completed project deliverables: Conducted with the customer or sponsor Results in formal sign-off on deliverables Different from quality control (which verifies correctness) Control Scope Control Scope monitors the status of the project scope and manages changes: Compare actual scope to the scope baseline Process scope change requests through integrated change control Update project documents as changes are approved Prevent scope creep — uncontrolled expansion of scope Scope Creep vs. Gold Plating

Issue Description Cause Scope Creep Uncontrolled changes or growth in scope Poor change control, stakeholder pressure Gold Plating Adding extra features not in the scope Team initiative without customer request Both are problematic because they consume resources without formal approval. Key Takeaways The Project Charter formally authorizes the project and establishes the project manager's authority Requirements documentation captures stakeholder needs through various elicitation techniques The Scope Statement defines what is included AND excluded from the project The WBS decomposes all project work following the 100% Rule The Scope Baseline consists of the Scope Statement, WBS, and WBS Dictionary Scope control prevents unauthorized changes through formal change management

Loading diagram... Scope Management Components

Test Your Knowledge

What does the 100% Rule in WBS construction mean?

The project must have 100% completion before delivery

The WBS must include 100% of the work required to complete the project scope

All team members must work at 100% capacity

Quality standards must be met 100% of the time Check Answer Need a hint? AI

Test Your Knowledge

Which document formally authorizes the project and gives the project manager authority to apply organizational resources?

Scope Statement

Work Breakdown Structure

Project Charter

Requirements Documentation Check Answer Need a hint? AI

Test Your Knowledge

What are the three components of the Scope Baseline?

Project Charter, Requirements, and WBS

Scope Statement, WBS, and WBS Dictionary

Requirements, Schedule, and Budget

Charter, Scope Statement, and Requirements Traceability Matrix Check Answer Need a hint? AI

Sections you finish are checked off in the contents.

Up Next 8.3 Schedule Management Continue learning

Independent exam preparation notice OpenExamPrep is an independent education provider, not affiliated with or endorsed by the exam sponsors named on this site. Exam and certification names identify what our resources help you study for; they do not imply sponsorship, approval, or review of our materials. Unless a resource expressly identifies authorized public material, our practice questions are independently developed simulations, not actual, recalled, or sponsor-provided exam items. We aim to reflect publicly available exam outlines and topic information in our study resources. Coverage, format, and difficulty may differ from the actual exam, and we cannot guarantee that every detail is accurate or current. Confirm exam requirements, fees, and policies with the official exam sponsor.