6.2 WBS, Work Packages, and Activity Definition

CAPM Certified Associate in Project Management Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Introduction & CAPM Exam Overview

1.1 About the CAPM Exam 1.2 PMBOK 7th Edition Overview 1.3 Exam Content Outline (ECO) 1.4 CAPM vs. PMP: Understanding the Differences

2 Chapter 2: Project Life Cycles and Processes (Domain 1, Tasks 1-2)

2.1 Projects, Programs, and Portfolios 2.2 Project Life Cycle Phases 2.3 The Five Process Groups 2.4 The Ten Knowledge Areas

3 Chapter 3: Project Management Planning (Domain 1, Task 2)

3.1 The Project Management Plan 3.2 Scope Management and the WBS 3.3 Schedule Management 3.4 Cost Management and Earned Value 3.5 Quality Management

4 Chapter 4: Project Roles, Responsibilities, and Ethics (Domain 1, Tasks 3-4)

4.1 Project Roles and Responsibilities 4.2 Leadership and Emotional Intelligence 4.3 Risk Management Fundamentals 4.4 PMI Code of Ethics and Professional Conduct 4.5 Problem-Solving Tools and Techniques

5 Chapter 5: Resource, Communication, and Stakeholder Management (Domain 1, Tasks 2-3)

5.1 Resource Management 5.2 Communications Management 5.3 Stakeholder Management 5.4 Procurement Management 5.5 Issues, Risks, Assumptions, and Constraints

6 Chapter 6: Predictive, Plan-Based Methodologies (Domain 2)

6.1 When to Use a Predictive Approach 6.2 WBS, Work Packages, and Activity Definition 6.3 Predictive Project Controls and Artifacts 6.4 Critical Path and Schedule Calculations

7 Chapter 7: Agile Frameworks and Methodologies (Domain 3, Tasks 1-3)

7.1 When to Use an Adaptive (Agile) Approach 7.2 The Scrum Framework 7.3 Kanban, XP, and SAFe 7.4 Agile Planning, Estimation, and Metrics 7.5 Agile Project Controls and Artifacts

8 Chapter 8: Business Analysis Roles and Stakeholder Communication (Domain 4, Tasks 1-2)

8.1 Business Analysis Roles and Responsibilities 8.2 Stakeholder Communication in Business Analysis 8.3 Business Case and Needs Assessment

9 Chapter 9: Requirements Gathering and Product Roadmaps (Domain 4, Tasks 3-4)

9.1 Requirements Gathering Approaches 9.2 Requirements Traceability Matrix 9.3 Product Roadmaps

10 Chapter 10: BA Methodologies and Requirements Validation (Domain 4, Tasks 5-6)

10.1 Business Analysis in Predictive and Agile Approaches 10.2 Acceptance Criteria and Requirements Validation 10.3 Business Analysis Tools and Techniques Summary

6.2 WBS, Work Packages, and Activity Definition

Key Takeaways Explain This Topic AI

The Work Breakdown Structure (WBS) is built by decomposition — subdividing deliverables into smaller, deliverable-oriented components

The 100% Rule requires that each level of the WBS captures all of the work of its parent, no more and no less

Work packages are the lowest WBS level; the 8/80 Rule suggests they take roughly 8 to 80 labor hours

The WBS dictionary documents each element (scope, deliverables, owner, acceptance criteria, assumptions, constraints)

Rolling wave planning elaborates near-term work in detail and leaves future work at a higher level — it is planned progressive elaboration, not scope creep

Last updated: June 2026

Decomposition and the WBS

The Work Breakdown Structure (WBS) is a deliverable-oriented hierarchical decomposition of the total scope of work the project team must execute. It is built through decomposition — subdividing project deliverables into smaller, more manageable components. A critical exam distinction: the WBS organizes deliverables (nouns) , not activities (verbs). Activities come later, during schedule planning.

Steps to create a WBS
Identify the major deliverables and the project-management work
Organize the deliverables into a logical hierarchy
Decompose upper-level deliverables into lower-level components
Assign identification codes (the WBS numbering scheme, e.g., 1.2.3)
Verify the result against the 100% Rule
Decomposition guidelines

Guideline What it means
Deliverable-oriented Elements are deliverables/outcomes, not tasks
100% Rule Each level represents exactly 100% of the work of its parent
Mutually exclusive No overlap between elements at the same level (avoids double-counting)
Appropriate detail Decompose only to the work package level
8/80 Rule A work package should take about 8 to 80 hours (some firms use 4/40)

The WBS Dictionary

The WBS dictionary is the companion document that gives detailed information about each WBS element so the work is unambiguous to whoever performs it.

Field Description
WBS code Unique identifier for the element
Work description Detailed statement of the work
Responsible organization Owner / who performs it
Schedule milestones Associated milestones
Resources required People, materials, equipment
Cost estimate Budgeted cost for the element
Quality requirements Standards the work must meet
Acceptance criteria How completion is verified
Assumptions and constraints Relevant limitations and presumptions

The scope baseline is a key exam term: it equals the approved scope statement + WBS + WBS dictionary together. A change to any of the three is a change to the scope baseline and must go through change control.

From Work Packages to Activities WBS -> Work Packages -> Activities -> Schedule

Concept Level Purpose
WBS element Deliverable hierarchy Organize scope
Work package Lowest WBS level Smallest deliverable unit; basis for estimating
Activity Below work packages Smallest schedulable unit of work
Milestone Key event Zero-duration marker

Define Activities decomposes each work package into the activities required to produce it. Each activity carries activity attributes : ID and name, predecessors and successors, logical relationships, leads and lags, resource requirements, and any imposed dates (date constraints).

Rolling Wave Planning

Rolling wave planning is a form of progressive elaboration : near-term work is planned in detail at the activity level, while work further out is held at a higher level — a planning package (a known work component below a control account but above work packages) or simply a coarse work package. As the project advances, those future components are elaborated into detailed activities.

Use it when:

The full scope cannot be defined in detail at the outset
Requirements for later phases depend on the results of earlier phases
The project is long and future conditions are uncertain

Key distinction (commonly tested): Rolling wave planning is NOT scope creep . The total scope is still captured (at a high level) in the WBS and stays controlled; only the level of detail increases over time. Scope creep, by contrast, is uncontrolled expansion of scope without change-control approval.

Milestones and the Milestone List

A milestone is a significant point or event in a project with zero duration — it consumes no time or resources itself; it marks the completion of a deliverable, phase, or other key event.

Milestone type Description
Mandatory Required by contract, regulation, or organizational policy
Optional Placed by the team to monitor progress internally
External Driven by factors outside the project (e.g., a vendor delivery)

Milestones drive schedule planning and progress tracking, stakeholder reporting, phase-gate reviews, and — in fixed-price work — contract payment triggers .

Worked example of the 100% Rule: A WBS element "3.0 Website" decomposes into 3.1 Front-end, 3.2 Back-end, and 3.3 Content. If 3.1 + 3.2 + 3.3 do not together cover everything the website requires (say, hosting setup was forgotten), the WBS violates the 100% Rule. The fix is to add the missing deliverable, not to inflate an existing branch.

Control Accounts and the Code of Accounts

Above the work-package level, related work packages may roll up into a control account — a management control point where scope, budget, and schedule are integrated and compared to earned value for performance measurement. Each control account can contain one or more work packages, and each work package belongs to exactly one control account. The code of accounts is the numbering system (1, 1.1, 1.1.2, and so on) that uniquely identifies every WBS component and lets costs and schedule roll up cleanly.

Why the WBS Matters Downstream

The WBS is not busywork; it is the foundation other planning processes depend on. Cost and duration estimates are built at the work-package level and aggregated upward. Risk identification uses the WBS to ensure no branch of scope is overlooked. The schedule is built from activities decomposed out of work packages. And scope verification ("Validate Scope") compares completed deliverables against WBS-defined acceptance criteria.

Common trap: Questions that list verbs ("write code," "test module") as WBS elements are testing whether you know the WBS holds deliverables, not activities . Activities belong in the activity list produced by the Define Activities process, one level below the work package.