# Work Breakdown Structure
A Work Breakdown Structure (WBS) is a project management tool that provides a hierarchical decomposition of the total scope of work. It breaks down a project into smaller, more manageable, and deliverable-oriented components, with the lowest level being a 'work package'.
**Pronunciation:** wurk brayk-doun struhk-cher
**Difficulty:** Beginner
**Synonyms:** WBS, Task Decomposition, Project Decomposition
**Categories:** Project Management, Planning
**Tags:** WBS, Project Planning, Scope Management, Task Decomposition, Deliverables
Canonical: https://scaleengineer.com/glossaries/work-breakdown-structure
---
## Definitions

- **Work Breakdown Structure in Project Management:** A **Work Breakdown Structure (WBS)** is a foundational project management tool that provides a deliverable-oriented, hierarchical decomposition of the total scope of work to be carried out by a project team. It visually breaks down a project into smaller, more manageable components, often called work packages.

**Key Concepts:**

*   **Hierarchical Nature:** The WBS organizes project work in a tree-like structure. The top level represents the final project deliverable, which is then broken down into subsequent levels of increasing detail.
*   **Deliverable-Oriented:** The focus of a WBS is on the outcomes or deliverables of the project, not the specific actions or tasks. For example, instead of 'Write Code', a WBS element would be 'User Authentication Module'.
*   **The 100% Rule:** This is a core principle of WBS construction. It states that the WBS must include 100% of the work defined in the project scope and capture all deliverables – internal, external, and interim. The sum of the work at the child levels must equal 100% of the work represented by the parent.
*   **Work Packages:** The lowest level of the WBS is known as a work package. This is the point at which the work can be reliably estimated, scheduled, assigned to a specific team or individual, and controlled.

**Example:**
For a project to build a new website, the WBS might look like this:

*   Level 1: New Corporate Website
    *   Level 2: Project Management
    *   Level 2: Design
        *   Level 3: Wireframes
        *   Level 3: Visual Mockups
    *   Level 2: Development
        *   Level 3: Front-End Development
        *   Level 3: Back-End Development
    *   Level 2: Content Creation
    *   Level 2: Testing & Deployment

**Usage:**
The WBS is a primary input for project planning. It is used to develop schedules, estimate costs and resources, assign responsibilities, and manage scope. It provides a clear framework for all stakeholders to understand the project's scope.

## Etymology

The term is a direct and descriptive combination of its components: 'Work' refers to the tasks and deliverables; 'Breakdown' signifies the process of decomposition or dividing into smaller parts; and 'Structure' denotes the resulting hierarchical arrangement.

## First used

Late 1950s

## Historical context

The concept of the Work Breakdown Structure was developed alongside the Program Evaluation and Review Technique (PERT) in the late 1950s. Its first major application was by the U.S. Department of Defense (DoD) for the Polaris missile program, a large and complex project that required meticulous planning and coordination.

Recognizing its effectiveness, the DoD mandated the use of the WBS, formalizing it in military standards like MIL-STD-881. This standard provided guidelines for creating consistent WBS across different defense projects. NASA also quickly adopted the WBS for its space programs, including the Apollo mission, where it was crucial for managing the immense scope and complexity.

Over time, the WBS concept moved from its military and aerospace origins into the commercial sector. The Project Management Institute (PMI) adopted it as a best practice and a core component of its Project Management Body of Knowledge (PMBOK® Guide), solidifying its status as a fundamental tool for professional project managers worldwide.

## Q&A

- **What is the '100% Rule' in the context of a Work Breakdown Structure?:** The 100% Rule is a core principle stating that the WBS must capture all the work defined in the project scope statement. It includes 100% of the deliverables—internal, external, and interim—and the work required to complete them. The sum of the work at the 'child' level must equal 100% of the work represented by the 'parent' level, ensuring no work is left out and no extra work is included.
- **What is the lowest level of a WBS called and what is its purpose?:** The lowest level of a Work Breakdown Structure is called a 'work package'. A work package is the point at which the work can be reliably estimated and managed. It's a specific, deliverable-focused component that can be assigned to an individual or a team, and for which cost and duration can be readily determined.
- **Is a WBS a schedule or a list of activities?:** No, a WBS is neither a schedule nor a simple list of activities. It is a hierarchical decomposition of the project's *deliverables* and scope. It defines *what* needs to be done, not *when* or *how*. The WBS serves as the foundation for developing the project schedule and activity list, but it is a distinct and separate artifact focused on the project's scope.

## Usage examples

- The project manager created a detailed **Work Breakdown Structure** to ensure all project deliverables were identified and organized.
- According to the **WBS**, the 'Develop User Interface' work package is assigned to the front-end team.
- To accurately estimate the project cost, we first need a complete **Project Decomposition** that outlines every component of the work.
- Without a clear **Work Breakdown Structure**, the project is at high risk of scope creep.

## Related terms

- Gantt Chart
- Critical Path Method
- Scope Creep
- Project Scope Statement
- Deliverable
- Work Package

## Popular related terms

- Gantt Chart
- Project Scope
- Deliverable