Create Work Breakdown Structure (WBS)

Sensei Short Scroll 7 Planning Process Group

Create Work Breakdown Structure (WBS)

Introduction: Why This Matters

Scope without structure is unmanageable. The Work Breakdown Structure (WBS) takes the high level scope statement and decomposes it into smaller, more manageable components. It is the bridge between what must be delivered and how the work will be planned, scheduled, costed, and executed.

On the PMP exam, the WBS is frequently tested as the foundation of the scope baseline. In practice, the WBS prevents missed deliverables, clarifies responsibilities, and enables accurate estimates for time and cost (Project Management Institute, 2021).

Purpose and Objectives

Primary Purpose: To subdivide project deliverables and work into smaller, manageable components called work packages.

Key Objectives:

  • Provide a structured breakdown of the entire project scope.
  • Facilitate accurate cost and schedule estimation.
  • Ensure nothing is forgotten (the 100 percent Rule).
  • Clarify accountability by linking deliverables to owners.
  • Produce the scope baseline (scope statement, WBS, WBS dictionary).

Overview

Create WBS takes the approved scope statement and requirements and converts them into a hierarchical, deliverable oriented structure. This structure becomes the backbone for later planning in schedule, cost, and resource management.

  • Scope translation: Changes narrative scope into visual, structured components.
  • Planning bridge: Connects scope definition to estimating, scheduling, and assigning work.

Characteristics

  • 100 percent Rule: The WBS must capture 100 percent of the scope, including project management work.
  • Deliverable oriented: Elements represent outputs, not individual tasks or activities.
  • Mutually exclusive: No overlap between WBS elements. Each deliverable belongs in one place.
  • Multi level: Starts with the entire project and decomposes into sub deliverables, then work packages.
  • Actionable: Work packages are small enough to be estimated, scheduled, and assigned to owners.

Inputs, Tools and Techniques, Outputs (ITTOs)

Inputs

  • Scope management plan.
  • Project scope statement.
  • Requirements documentation.
  • Enterprise environmental factors.
  • Organizational process assets.

Tools and Techniques

  • Decomposition: Breaking down deliverables into smaller, more manageable components.
  • Expert judgment: Leveraging subject matter experts to structure work.

Outputs

  • Scope baseline (scope statement, WBS, WBS dictionary).
  • Project document updates.

The WBS Structure

Levels of the WBS

  • Level 1: Entire project.
  • Level 2: Major deliverables or phases.
  • Level 3 and below: Sub deliverables, broken down until work packages are defined.

Work packages

  • Lowest level of the WBS.
  • Can be estimated for time and cost.
  • Assignable to a specific person, team, or vendor.

WBS dictionary

  • Companion document that provides details about each WBS element, such as description, owner, acceptance criteria, and resource or cost information.

Practical Example

Context: Website Development Project.

Scope statement: Create a new e commerce website for a retail company.

WBS structure:

  • Level 1: E commerce Website Project
    • Level 2: Website Design
      • Level 3: Wireframes
      • Level 3: Graphic Design
    • Level 2: Website Development
      • Level 3: Front end development
      • Level 3: Back end development
    • Level 2: Testing and Quality Assurance
      • Level 3: Functional testing
      • Level 3: Security testing
    • Level 2: Deployment
      • Level 3: Hosting setup
      • Level 3: Go live activities
    • Level 2: Project Management
      • Level 3: Reporting
      • Level 3: Stakeholder engagement

WBS dictionary example entry:

  • Work package: Security testing.
  • Description: Perform penetration testing and vulnerability scans.
  • Responsible: QA team and external vendor.
  • Acceptance criteria: No critical vulnerabilities remain unresolved.
  • Cost estimate: $25,000.

Common Pitfalls

Task oriented WBS

  • Pitfall: Breaking work into tasks such as “design homepage mock up” instead of deliverables.
  • Prevention: Keep the focus on deliverables, not individual actions.

Incomplete WBS

  • Pitfall: Missing deliverables lead to surprise work later.
  • Prevention: Apply the 100 percent Rule and validate the WBS against the scope statement.

Too much detail

  • Pitfall: Micromanagement and unnecessary administrative overhead.
  • Prevention: Stop decomposition when work can be reasonably estimated, scheduled, and assigned.

No WBS dictionary

  • Pitfall: Ambiguity around what each WBS element really includes.
  • Prevention: Always supplement the WBS with dictionary entries for clarity.

Sensei Tip : A strong WBS is the project’s skeleton. If the structure is solid and complete, the schedule and budget have a much better chance of standing firm.

Exam Alert : When a question is about confusion over what work is included in the project, and one of the options is the Work Breakdown Structure, that is usually the best answer because the WBS reflects 100 percent of the scope.

Exam Lens

Patterns on the PMP Exam:

  • The WBS is part of the scope baseline and must be developed before detailed scheduling and costing.
  • If asked what to do when scope is unclear or work is not fully understood, the correct step is usually to create or refine the WBS.
  • Deliverables, not tasks, belong in the WBS.
  • WBS dictionary details often appear in questions about clarifying what a deliverable includes and who is responsible.

Sample Question

Question: A project team begins creating schedules but disagrees on what work should be included. What should the project manager consult first?

  1. Activity list.
  2. Requirements documentation.
  3. Project scope statement.
  4. Work Breakdown Structure.

Correct Answer: D. The WBS provides the structured breakdown of all deliverables.

Quick Recap Table

Element Why It Matters Exam Watch Point
WBS Deliverable based breakdown of the entire project scope. Always deliverable oriented, not task based.
Work packages Smallest manageable components for estimating and assignment. Must be estimable and assignable to an owner.
Scope baseline Scope statement, WBS, and WBS dictionary together. Know exactly what forms the scope baseline.
100 percent Rule Ensures the WBS includes all project scope and project management work. Commonly tested concept whenever missed work or surprise deliverables appear.

Key Takeaways

  • The WBS decomposes the project scope into manageable components called work packages.
  • The scope baseline consists of the scope statement, WBS, and WBS dictionary and is the reference point for all scope control.
  • The WBS must follow the 100 percent Rule, be deliverable oriented, and avoid overlap between elements.
  • On the PMP exam, questions about scope baselines, missing work, or unclear deliverables often point back to the WBS and its dictionary.

Next Step

With the WBS complete, the project has a clear structure for all deliverables. The next processes move into schedule planning, starting with Plan Schedule Management.

Bibliography

Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (Project Management Body of Knowledge Guide) (7th ed.). Project Management Institute.

Scroll to Top