Planning & Execution

Work Breakdown Structure: Decomposing Projects into Manageable Pieces

By Vact Published · Updated

A Work Breakdown Structure (WBS) is a hierarchical decomposition of a project into smaller, manageable components. It answers the question “what needs to be done?” by breaking the project down from the top-level deliverable into progressively smaller pieces until each piece is small enough to estimate, assign, and track. The WBS is a foundational project planning tool used across waterfall, agile, and hybrid methodologies.

How a WBS Works

A WBS is organized in levels:

Level 1: The project itself. Level 2: Major deliverables or phases. Level 3: Sub-deliverables or components. Lowest level: Work packages that can be estimated, assigned, and checked. A branch can reach this point at a different depth from another branch.

Example for a mobile app project:

1. Mobile App Launch
  1.1 User Authentication
    1.1.1 Login screen
    1.1.2 Registration flow
    1.1.3 Password reset
    1.1.4 Social login integration
  1.2 Core Features
    1.2.1 Dashboard
    1.2.2 Profile management
    1.2.3 Notification system
  1.3 Backend Infrastructure
    1.3.1 API development
    1.3.2 Database setup
    1.3.3 Hosting configuration
  1.4 Quality Assurance
    1.4.1 Test plan creation
    1.4.2 Automated testing
    1.4.3 User acceptance testing
  1.5 Deployment
    1.5.1 App store submission
    1.5.2 Production deployment
    1.5.3 Monitoring setup

The 100% Rule

The WBS must include 100% of the work defined by the project scope. Everything in the scope statement must appear somewhere in the WBS, and nothing outside the scope should appear. This rule ensures that the WBS is complete and that no work is accidentally omitted from planning.

Deliverable-Oriented vs. Phase-Oriented

Deliverable-Oriented WBS

Organized by what is produced. The Level 2 items are the project’s major deliverables. This approach works well for product development where the focus is on what the customer receives.

Phase-Oriented WBS

Organized by when work happens. The Level 2 items are project phases: Requirements, Design, Development, Testing, Deployment. This approach aligns with waterfall methodology and is common in construction and engineering.

A deliverable-oriented structure can help a team check product scope before turning the work into a schedule or backlog.

WBS and Agile

One possible mapping to a tool hierarchy is shown below. Adapt it to the product and the way your team organizes work:

WBS LevelAgile Equivalent
Level 1Product/Project
Level 2Epic
Level 3Feature/User Story
Level 4Task/Subtask

The WBS is typically created during project scoping or release planning and then translated into epics and stories in the PM tool. Keep the scope structure and the evolving backlog aligned, while allowing the backlog to contain changing priorities and discoveries.

Creating a WBS

Step 1: Start with Deliverables

List the major deliverables from the project scope. These become Level 2 items.

Step 2: Decompose Each Deliverable

For each deliverable, ask “what components make up this deliverable?” Continue decomposing until you reach work packages that meet these criteria:

  • Estimable: The team can provide a realistic duration or effort estimate
  • Assignable: A single person or small team can take ownership
  • Observable: Progress is visible and completion is verifiable
  • Sized appropriately: Small enough to estimate and verify, with a level of detail that suits the project and reporting cycle

Step 3: Verify Completeness

Walk through the WBS with the team and stakeholders. For each Level 2 item, ask “if we complete all the Level 3 items under this, is the deliverable truly complete?” The answer must be yes for the WBS to follow the 100% rule.

Step 4: Number and Document

Assign WBS numbers (1.1, 1.1.2, etc.) and document each work package with a brief description. This numbering system is used throughout the project for task tracking, dependency mapping, and status reporting.

WBS Pitfalls

Decomposing too deeply. Breaking a task into sub-tasks into sub-sub-tasks creates a WBS that is too granular to manage. Stop when work packages are small enough to estimate and track but large enough to represent meaningful progress.

Confusing the WBS with a schedule. The WBS defines what needs to be done, not when. Scheduling happens after the WBS is created by adding durations, dependencies, and resource assignments. The WBS feeds into the schedule but is not the schedule.

Missing non-obvious work. Project management activities, documentation, testing, deployment, and training are often omitted from the WBS because they are less visible than feature development. Ensure the WBS includes all work needed to deliver the project, not just the development work.

Creating the WBS alone. The project manager should facilitate WBS creation, but the team should contribute. Developers identify technical components the PM may miss. Designers identify UX work. QA identifies testing activities. Collaborative creation produces a more complete WBS.

Write a dictionary entry for each work package

The label “help articles” leaves several questions unanswered. A dictionary entry can specify the 12 article topics, the required product version, the editor, the reviewer, and the evidence of completion. Add the exclusions: translation and video production, for example, may belong to a later release. Record the assumptions behind the estimate, such as access to a product specialist.

Use these fields: WBS identifier, deliverable, scope included, scope excluded, owner, acceptance criteria, estimate basis, dependencies, and evidence link. A package is complete when the agreed result exists and passes its acceptance check. Spending the estimated hours does not establish completion by itself.

Check for gaps and double counting

Suppose the project includes articles, a search configuration, a launch page, and staff training. Ask who owns screenshots, accessibility checks, redirects from old pages, and the training material. Give each piece of work a clear home. If both the article package and the launch package include the same screenshots, assign the production work once and link the dependency from the other package.

Walk the structure from the bottom up. The children under “help articles” should collectively produce the whole article deliverable. Then check the top level against the approved scope. Keep an unresolved item visible with an owner rather than silently omitting it because its estimate is difficult.

Move from scope to a schedule

After the packages are clear, identify the activities needed to produce each result. Assign durations and relationships to those activities. An article may need drafting, technical review, revision, and publication; the work package describes the accepted result, while the schedule describes when those activities can happen.

Keep the WBS identifier in your task list and cost records so that related information can be traced back to the same scope. When the scope changes, update the affected dictionary entry and assess its effect on the schedule and budget together.

Sources