Study guide
6.2 Product Breakdown Structures (PBS) and Work Breakdown Structures (WBS)
APM Project Fundamentals Qualification PFQ
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Project Management & Operating Environment
1.1 Projects vs Business as Usual (BAU) 1.2 Programmes, Portfolios, and Strategic Alignment 1.3 Operating Environment and PESTLE Analysis
2 Chapter 2: Project Life Cycles
2.1 Linear Project Life Cycles and Phase Gates 2.2 Iterative and Hybrid Life Cycles 2.3 Extended Life Cycles, Handover, and Benefits Realization
3 Chapter 3: Roles, Governance & Organization
3.1 The Project Sponsor and Governance Board 3.2 The Project Manager and Project Team 3.3 Users, Product Owners, and the Project Management Office (PMO)
4 Chapter 4: Business Case, Benefits & Stakeholders
4.1 Purpose, Content, and Roles in Developing the Business Case 4.2 Benefits Management and Value Tracking 4.3 Stakeholder Analysis and Engagement Matrix
5 Chapter 5: Project Management Plan & Estimating
5.1 Project Management Plan (PMP) and Deployment Baselines 5.2 Estimating Methods and the Estimating Funnel 5.3 Project Reporting, Variance Tracking, and Success Criteria
6 Chapter 6: Scope Definition & Breakdown Structures
6.1 Scope Management Principles in Linear vs Iterative Delivery 6.2 Product Breakdown Structures (PBS) and Work Breakdown Structures (WBS) 6.3 OBS, CBS, and the Responsibility Assignment Matrix (RACI)
7 Chapter 7: Change Control & Configuration Management
7.1 Requirements Definition and Acceptance Criteria 7.2 The Change Control Process and Impact Assessment 7.3 Configuration Management and Version Verification
8 Chapter 8: Schedule Planning & Critical Path
8.1 Scheduling Principles, Gantt Charts, and Milestones 8.2 Critical Path Analysis, Dependencies, and Float 8.3 Time Boxing and Iterative Schedule Control
9 Chapter 9: Resource Optimization & Procurement
9.1 Resource Optimization: Allocation, Smoothing, and Levelling 9.2 Procurement Strategy and Supplier Selection 9.3 Contract Types and Supplier Reimbursement Methods
10 Chapter 10: Risk and Issue Management
10.1 Principles of Risk Management and the Risk Process 10.2 Threat and Opportunity Response Strategies 10.3 Risk Registers, Ownership, and Risk vs Issue Distinction 10.4 Issue Management Process, Escalation, and Governance
11 Chapter 11: Quality Management & Project Reviews
11.1 Quality Definitions, Management, and Quality Planning 11.2 Quality Assurance vs Quality Control 11.3 Project Reviews, Decision Gates, and Audits
12 Chapter 12: Project Communication Management
12.1 Principles of Project Communication and Communication Models 12.2 Communication Methods: Advantages, Limitations, and Barriers 12.3 Developing and Benefiting from a Project Communication Plan
13 Chapter 13: Leadership, Teams & Conflict
13.1 Leadership Styles and Influencing Team Performance 13.2 Team Development Models: Tuckman and Belbin 13.3 Team Challenges, Conflict Resolution, and Collaboration
6.2 Product Breakdown Structures (PBS) and Work Breakdown Structures (WBS)
Key Takeaways Explain This Topic AI
Breakdown structures decompose complex project endeavors into smaller, hierarchical, and manageable components to facilitate accurate estimating, scheduling, budgeting, and accountability.
A Product Breakdown Structure (PBS) is a deliverable-oriented decomposition defining 'what' is produced using nouns, while a Work Breakdown Structure (WBS) decomposes total work effort using action verbs.
The 100% Rule is the fundamental governing principle of breakdown structures, stating that the WBS must encompass 100% of the project scope—including management and assurance—no more and no less.
A Work Package represents the terminal (lowest) level of the WBS; it is a discrete, manageable unit of work bounded by a defined budget, duration, and single-point responsibility.
The WBS Dictionary accompanies the visual WBS diagram, providing comprehensive scope boundary descriptions, acceptance criteria, assumptions, and resource assignments for every work package.
Last updated: September 2026
6.2 Product Breakdown Structures (PBS) and Work Breakdown Structures (WBS)
Core Concept: Human beings struggle to comprehend and manage large, monolithic endeavors. Decomposition is the foundational analytical technique of breaking down a complex project into progressively smaller, more manageable hierarchical components until they can be accurately estimated, scheduled, assigned, and controlled.
In project delivery, attempting to plan and manage a multi-million-pound engineering scheme, software implementation, or organizational restructuring as a single entity invites disaster. Without structured decomposition, work tasks are overlooked, duplicate effort occurs, dependencies remain invisible, and cost estimates prove wildly inaccurate.
The Association for Project Management (APM) defines two primary hierarchical structures to structure scope: the Product Breakdown Structure (PBS) and the Work Breakdown Structure (WBS) . Together, they provide the structural spine that underpins scheduling, cost management, resource allocation, and risk management.
Product Breakdown Structure (PBS)
A Product Breakdown Structure (PBS) is a hierarchical decomposition of the tangible and intangible deliverables (products) that the project will produce. It focuses purely on "what" is being created. +-----------------------------------------------------------------------------------------+
- | PRODUCT BREAKDOWN STRUCTURE (PBS) |
- | Focus: WHAT is being produced |
- | Language: Exclusively NOUNS |
- +-----------------------------------------------------------------------------------------+
- | LEVEL 1: Complete Train |
- | | |
- | +----------------------------------+----------------------------------+ |
- | | | | |
- | LEVEL 2: Carriage Shell LEVEL 2: Propulsion System LEVEL 2: Interior Fit-out |
- | | | | |
- | +-----+-----+ +-----+-----+ +-----+-----+ |
- | | | | | | | |
- | L3: Chassis L3: Roof Panel L3: Traction L3: Inverter L3: Seating L3: Lighting |
- +-----------------------------------------------------------------------------------------+
Core Characteristics of a PBS:
Noun-Oriented: Every element in a PBS is expressed strictly as a noun or noun phrase (e.g., "Propulsion System", "Braking Assembly", "Mobile Application", "User Training Manual"). It never contains verbs, actions, or processes.
Deliverable-Focused: It depicts the physical or functional anatomy of the final product and its sub-assemblies. It asks: What components make up the finished asset?
Product Descriptions: Each leaf product on the PBS is supported by a formal Product Description document, defining its purpose, physical composition, source materials, quality criteria, performance tolerances, and acceptance testing methods.
Product Flow Diagrams (PFD): Once the PBS is established, the project team can construct a Product Flow Diagram to map the sequential assembly logic and dependencies among products (e.g., the chassis must be fabricated before the seating can be installed).
Work Breakdown Structure (WBS)
While the PBS identifies what products exist, it does not describe the effort, activities, and operational tasks required to build, test, integrate, and manage them. This is the domain of the Work Breakdown Structure (WBS) .
A Work Breakdown Structure (WBS) is a hierarchical decomposition of the total scope of work to be performed by the project team to accomplish the project objectives and create the deliverables identified in the PBS. It focuses on "how" and "what work" will be executed.
Core Characteristics of a WBS:
Work-Oriented: Elements in a WBS are expressed as work streams, activity phases, or verb-noun deliverables (e.g., "Fabricate Carriage Shell", "Assemble Propulsion System", "Execute Dynamic Track Testing", "Project Management & Governance").
Comprehensive Scope Representation: Unlike the PBS (which only contains physical or digital deliverables), the WBS captures 100% of the effort required on the project, explicitly including project management, procurement administration, safety inspections, systems integration, and handover.
Hierarchy of Detail: The WBS decomposes downward from the overall project goal (Level 1), through sub-projects or major delivery phases (Level 2), system packages (Level 3), down to the terminal elements: Work Packages .
Comparative Analysis: PBS vs WBS
Dimension Product Breakdown Structure (PBS) Work Breakdown Structure (WBS)
Primary Focus "What" is being created (outputs and products). "How" and "What work" must be done to produce the outputs.
Linguistic Convention Strictly nouns or noun phrases (e.g., "Brake Assembly", "Database Schema"). Verbs or action-oriented phrases (e.g., "Install Brakes", "Configure Database").
Lowest Level Element Component, sub-assembly, or physical product part. Work Package (the smallest unit of managed work).
Scope Boundaries Restricted to tangible/intangible project deliverables and components. Encompasses total project effort, including project management, testing, and assurance.
Supporting Documentation Product Descriptions (defining form, fit, function, and quality criteria). WBS Dictionary (defining scope boundaries, milestones, budgets, and owners).
Downstream Utility Used to construct Product Flow Diagrams (PFDs) and determine technical assembly logic. Used to build the project schedule (Gantt chart/network diagrams), CBS, and RACI matrix.
The 100% Rule
The 100% Rule is the universal golden standard governing the construction and integrity of breakdown structures, articulated by the APM and global project standards.
The 100% Rule: The Work Breakdown Structure must encompass 100% of the project scope defined in the project baseline—including project management, governance, assurance, and support activities—with no omitted scope and no extraneous scope . +--------------------------+
- | Level 1: Project Scope |
- | (100%) |
- +-------------+------------+
- |
- +-------------------------+-------------------------+
- | |
- +------------------+ +------------------+
- | Level 2: Phase A | | Level 2: Phase B |
- | (60%) | | (40%) |
- +--------+---------+ +--------+---------+
- | |
- +-----+-----+ +-----+-----+
- | | | |
- +------+ +-------+ +-------+ +-------+
- | L3: | | L3: | | L3: | | L3: |
- | WP 1 | | WP 2 | | WP 3 | | WP 4 |
- |(35%) | |(25%) | |(20%) | |(20%) |
- +------+ +-------+ +-------+ +-------+
- [35% + 25% = 60%] [20% + 20% = 40%]
Critical Dimensions of the 100% Rule:
Child Sum Equals Parent: Symmetrically across every level of the hierarchy, the sum of the work represented by child elements must equal exactly 100% of the parent element above them. A Level 2 parent consisting of three Level 3 children must be completely and exclusively satisfied when those three children are delivered.
No Scope Gaps: If a task or deliverable is required to achieve the project objectives, it must appear in the WBS. If it is omitted from the WBS, it will not be estimated, scheduled, or budgeted, inevitably causing project delays and cost overruns.
No Extraneous Scope: The WBS must not contain any work that falls outside the approved project scope baseline. Including extraneous tasks invites scope creep and wastes resources.
Inclusion of Non-Deliverable Work: The 100% rule mandates that overhead effort—such as stage-gate governance, progress reporting, supplier auditing, stakeholder engagement workshops, and commissioning—must be represented as formal WBS elements.
Work Packages: The Terminal Units of Control
A Work Package is the terminal element at the lowest level of decomposition along any branch of the WBS. It represents the point at which work is sufficiently granular to be planned, executed, monitored, and controlled as a single unit.
Essential Criteria for a Work Package:
Single Accountability: Assigned to a single named individual, work package manager, or external contractor who holds single-point accountability for its completion.
Finite Duration and Boundaries: Characterized by an identifiable start milestone and a distinct completion milestone, typically spanning between a few days and several weeks (often calibrated to match regular project reporting cycles).
Discrete, Measurable Deliverable: Produces an objective, verifiable output (e.g., an engineered blueprint, a foundation slab, a tested software module) that can be independently audited against pre-agreed quality standards.
Estimable Cost and Resources: Bounded by a dedicated financial budget (labor hours, material costs, subcontractor fees) that can be tracked for variance.
Basis for Downstream Control: Work packages form the building blocks for network diagramming (precedence relationships), Critical Path Method (CPM) scheduling, resource leveling, and Earned Value Management (EVM).
The WBS Dictionary
A visual tree diagram of a WBS is inherently limited; boxes containing brief titles like "1.3.2 Assemble Circuit Boards" cannot convey detailed technical parameters, boundaries, or acceptance criteria. Attempting to rely solely on the diagram creates severe ambiguity.
The WBS Dictionary is a companion document that provides detailed, narrative metadata for every single element and work package within the WBS.
Key Information Documented in a WBS Dictionary Entry:
Code of Accounts Identifier: A standardized alphanumeric numbering code (e.g., WBS 2.4.1) that links the work package to the project schedule and financial cost codes;
Work Package Title and Narrative: A detailed description of the work scope to be executed;
Scope Boundaries (Inclusions and Exclusions): Explicit statements defining what work is included within the package, and crucially, what related work is explicitly excluded and assigned elsewhere;
Assigned Owner: The named individual, functional team, or subcontractor holding single-point delivery responsibility;
Input Prerequisites: Predecessor dependencies, raw materials, or specifications required before work can commence;
Deliverables and Acceptance Criteria: The specific, verifiable outputs that must be produced, along with the technical standards, tolerances, and inspection checklists required for sign-off;
Resource Allocation and Budget: Allocated labor hours, non-labor expenses, specialized machinery, and authorized cost ceiling;
Milestone Schedule: Planned start date, intermediate review milestones, and target completion date.