A temporary endeavor undertaken to create a unique product, service, or result.

The uncontrolled expansion to product or project scope without adjustments to time, cost, and resources.

An individual, group, or organization who may affect, be affected by, or perceive itself to be affected by a decision, activity, or outcome of a project, program, or portfolio.

Predictive Scope Management and the Work Breakdown Structure — CAPM Mastery: Comprehensive Exam-Ready Preparation for the 2023+ CAPM Blueprint

From Vague Idea to Clear Scope (Predictive Projects)

Why Scope Matters in Predictive Projects

In predictive projects, you lock down scope early and then protect it. The CAPM tests how well you can plan and control that scope.

Predictive Life Cycle Definition

A predictive life cycle is: "A development life cycle in which the project scope, time, and cost are determined in the early phases of the life cycle."

Scope Planning Flow

You capture requirements, define product and project scope, build a WBS, then form the scope baseline to guide and control the work.

Three Exam Ideas

1) Predictive = plan-driven. 2) WBS is about deliverables and work. 3) Scope control relies on the scope baseline and formal change control.

Product Scope vs Project Scope

Two Flavors of Scope

Product scope is what the product must be and do. Project scope is the work needed to create that product with those features.

Product Scope Example

For a mobile banking app, product scope includes biometric login, balance views, transfers, bill pay, and notifications.

Project Scope Example

For the same app, project scope includes workshops, UX design, coding, testing, security audits, training, and deployment.

Exam Angle

Changes to features = product scope. Changes to tasks to achieve the same features = project scope. Stakeholders and governance shape both.

From Requirements to Scope: The Linkage

Scope Starts With Requirements

Scope flows from stakeholder requirements, not from thin air. You collect and organize needs before defining scope.

Stakeholders and Needs

Stakeholders are individuals or groups who may affect or be affected by the project. They provide needs, expectations, and constraints.

The RTM Bridge

A requirements traceability matrix is "A grid that links product requirements from their origin to the deliverables that satisfy them."

Define Scope and Build WBS

Approved requirements feed into the project scope statement, which then gets decomposed into a WBS for planning and control.

The Work Breakdown Structure (WBS): Core Definition

Know This Definition Cold

A 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."

Hierarchy and 100% Rule

The WBS breaks the whole project into levels. It should cover 100% of the project scope; what is not in the WBS is out of scope.

Deliverable-Oriented

The WBS is organized around deliverables and outcomes, not people or dates. Schedule and assignments come after the WBS.

Common Exam Traps

Do not confuse WBS with a schedule or with an activity list. WBS first: what work and deliverables; activities and timing come later.

Reading a Simple WBS: Website Project

Website WBS Overview

Example project: "Corporate Marketing Website Redesign". Level 1 is the whole project; Level 2 are major deliverables or phases.

Sample WBS Structure

Corporate Website 1.1 Requirements & Design 1.2 Content 1.3 Development & Testing 1.4 Deployment & Training.

Deeper Levels

Under 1.3 Development & Testing you might see 1.3.1 Front-End Build, 1.3.2 CMS Config, 1.3.3 System and UAT Testing.

Spotting Work Packages

You keep decomposing until you reach work packages. Those lowest-level boxes are where you estimate and manage cost and duration.

Work Packages: The Manageable Units of Work

Work Package Definition

A work package is "The work defined at the lowest level of the work breakdown structure for which cost and duration are estimated and managed."

Role of Work Packages

Work packages sit at the lowest WBS level. This is where you attach cost and duration estimates and manage performance.

From Work Package to Activities

A work package like "Home Page Template" may generate several schedule activities: design, code, integrate, and test.

Exam Traps

Do not confuse work packages with single tasks, or estimate only at high levels when the question expects work package-level planning.

The Scope Baseline: Scope Statement, WBS, WBS Dictionary

What Is the Scope Baseline?

The scope baseline is the official reference for what is in scope. It includes the scope statement, the WBS, and the WBS dictionary.

Scope Statement and Acceptance

The scope statement describes scope and deliverables and includes acceptance criteria: "A set of conditions that is required to be met before deliverables are accepted."

WBS and WBS Dictionary

The WBS shows the structure of work. The WBS dictionary adds details for each element, like descriptions, owners, and specific acceptance criteria.

Using the Baseline

To control scope and avoid scope creep, compare proposed work to the scope baseline and route changes through formal change control.

Thought Exercise: Decomposing a Simple Project

Try this short exercise to practice thinking in WBS terms.

Scenario: You are managing a predictive project to organize a one-day university tech conference with 200 attendees.

Identify major deliverables (Level 2)

Without worrying about details, list 4–6 major deliverables or components that must exist for the conference to be considered successful.
Examples might include: Venue and Logistics, Speakers and Agenda, Marketing and Registration, On-site Operations, Post-Event Wrap-up.

Break down one deliverable (Level 3)

Pick one major deliverable you listed.
Write 3–5 sub-deliverables or work components under it.
For example, under "Marketing and Registration" you might have: Event Website, Registration System Setup, Email Campaign, Social Media Promotion.

Identify a work package

Choose one sub-deliverable and ask: "Can I reasonably estimate cost and duration for this as a unit?" If yes, it might be a work package.
If it still feels too large or vague, decompose it further.

Check alignment with requirements

Imagine a requirement: "The conference must support online payment and issue automatic email confirmations." Which WBS element(s) would satisfy this requirement?
This is how you mentally link the requirement to deliverables and, eventually, to the requirements traceability matrix.

Pause for 3–4 minutes and actually jot down your WBS fragments. This kind of mental practice will make WBS questions feel much more natural on the exam.

Quick Check: Product vs Project Scope and WBS Basics

Test your understanding of core distinctions before we go deeper.

A bank is launching a new credit card. Which option best represents **project scope** (not product scope) in a predictive life cycle?

The credit card's interest rate, rewards structure, and annual fee
The tasks required to design, develop, test, and launch the credit card offering
The list of features that customers expect in a modern credit card
The long-term market share target for the new credit card

Show Answer

Answer: B) The tasks required to design, develop, test, and launch the credit card offering

Project scope is the work needed to deliver the product. Option B describes tasks to design, develop, test, and launch the card. Option A and C are product scope (features and characteristics). Option D is a business objective, not directly project scope.

Quick Check: Work Packages and Scope Baseline

Another short quiz to reinforce key definitions and how they are used.

During execution, a team member suggests adding an extra reporting feature "because we have time". What should the project manager do FIRST in a predictive project?

Accept the idea and let the team implement it to delight the customer
Reject the idea immediately because it was not in the original plan
Check the scope baseline and follow the change control process to evaluate the impact
Update the WBS dictionary informally and proceed with the change

Show Answer

Answer: C) Check the scope baseline and follow the change control process to evaluate the impact

In predictive projects, the scope baseline (scope statement, WBS, WBS dictionary) is the reference. Any new feature must be evaluated through formal change control. Option C is correct. Option A is gold plating. Option B ignores potentially valuable change. Option D bypasses governance.

Flashcards: Core Scope and WBS Terms

Use these flashcards to lock in the exact wording of key PMI definitions and related concepts.

project: A temporary endeavor undertaken to create a unique product, service, or result.
predictive life cycle: A development life cycle in which the project scope, time, and cost are determined in the early phases of the life cycle.
work breakdown structure: 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.
work package: The work defined at the lowest level of the work breakdown structure for which cost and duration are estimated and managed.
requirements traceability matrix: A grid that links product requirements from their origin to the deliverables that satisfy them.
acceptance criteria: A set of conditions that is required to be met before deliverables are accepted.
product scope (concept): The features and functions that characterize a product, service, or result (what the product must be and do).
project scope (concept): The work that needs to be accomplished to deliver a product, service, or result with the specified features and functions.
scope baseline components: Project scope statement, WBS, and WBS dictionary used together as the approved scope reference.

Controlling Scope and Preventing Scope Creep

What Is Scope Creep?

Scope creep is uncontrolled expansion of product or project scope without corresponding changes to time, cost, and resources.

Control Scope Using the Baseline

You measure work against the scope baseline: WBS, scope statement, and WBS dictionary with their acceptance criteria.

Handle Change Requests

When new features are requested, analyze impact, use the requirements traceability matrix, and route through formal change control.

Exam Signal Words

Strong answers mention the scope baseline, change control, and updating the WBS/WBS dictionary, not quietly doing extra work.

Mini Scenario: Interpreting a WBS on the Exam

Imagine this simplified WBS for a "Data Migration Project":

Data Migration Project

1.1 Source Data Analysis

1.1.1 Identify Source Systems

1.1.2 Profile Data Quality

1.2 Migration Development

1.2.1 Design Migration Scripts

1.2.2 Develop Migration Scripts

1.2.3 Unit Test Scripts

1.3 Execution and Validation

1.3.1 Trial Migration

1.3.2 Full Migration

1.3.3 Post-Migration Validation

Thought questions (answer mentally or jot them down):

Which elements are most likely work packages?

Hint: Look for the lowest-level items that you could estimate and manage.

A stakeholder asks, "Can we also add a real-time data sync feature?" Where do you look first?

Think: Does any existing WBS element cover this? If not, what process do you follow?

A CAPM question shows this WBS and asks: "Where should cost and duration be estimated and managed?" Which definition should you recall?

Hint: It involves the lowest level of the WBS.

If "Post-Migration Validation" fails to meet a requirement like "all customer records must be 100% accurate after migration," which artifact helps you prove what was originally agreed?

Think about acceptance criteria and the requirements traceability matrix.

This is how many exam questions are structured: a short WBS plus a twist about change, estimation, or acceptance. Practice spotting the relevant part of the WBS and linking it back to definitions.

Key Terms

project: A temporary endeavor undertaken to create a unique product, service, or result.
scope creep: The uncontrolled expansion to product or project scope without adjustments to time, cost, and resources.
stakeholder: An individual, group, or organization who may affect, be affected by, or perceive itself to be affected by a decision, activity, or outcome of a project, program, or portfolio.
work package: The work defined at the lowest level of the work breakdown structure for which cost and duration are estimated and managed.
product scope: The features and functions that characterize a product, service, or result.
project scope: The work performed to deliver a product, service, or result with the specified features and functions.
scope baseline: The approved version of a scope statement, work breakdown structure (WBS), and its associated WBS dictionary, which can be changed only through formal change control procedures and is used as a basis for comparison.
acceptance criteria: A set of conditions that is required to be met before deliverables are accepted.
adaptive life cycle: A development life cycle that is agile, iterative, or incremental. The detailed scope is defined and approved before the start of an iteration.
predictive life cycle: A development life cycle in which the project scope, time, and cost are determined in the early phases of the life cycle.
work breakdown structure: 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.
requirements traceability matrix: A grid that links product requirements from their origin to the deliverables that satisfy them.