A work breakdown structure (WBS) template provides a hierarchical decomposition framework for dividing the total project scope into progressively smaller, manageable components until the work is defined at the work package level — the lowest level at which cost and duration can be reliably estimated and managed. According to the Project Management Institute (PMI), the WBS is a key output of the Develop Scope Structure process in the Scope Performance Domain of PMBOK 8, and together with the project scope statement and the WBS dictionary, it constitutes the scope baseline — the approved foundation against which all scope performance is measured.

What is a Work Breakdown Structure?

In PMBOK 8, the work breakdown structure (WBS) is a hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables. Each descending level of the WBS represents an increasingly detailed definition of the project work. At the lowest level of the WBS is the work package — a deliverable or project work component at the level at which cost and duration can be estimated and managed. Each work package has a unique identifier that provides a structure for hierarchical summation of costs, schedule, and resource information. In agile projects, the WBS corresponds to the product backlog, where work items can be broken down into epics, features, and user stories. The WBS provides a strategic view of the project's scope, ensuring that all team members are aligned and working toward a common goal.

What's Included in This Work Breakdown Structure Template?

• WBS Hierarchy - The complete decomposition of project scope from the project level down through deliverables, sub-deliverables, and work packages, displayed as a tree diagram or indented outline with a consistent numbering scheme.
• WBS Code of Accounts - Unique identifiers for each WBS element (e.g., 1.0, 1.1, 1.1.1) that link WBS components to cost accounts, schedule activities, and resource assignments, enabling integrated performance measurement.
• Work Package Descriptions - Brief descriptions of each work package defining the scope of the work, the deliverable produced, and the acceptance criteria, providing enough detail to assign, track, and measure the work.
• Responsible Party - The team member, department, or organizational unit accountable for delivering each work package, establishing clear ownership at the lowest level of the WBS.
• WBS Dictionary Reference - Pointers to the WBS dictionary entries that provide detailed information about each WBS component, including scope description, milestones, resource requirements, cost estimates, and quality requirements.
• Level of Decomposition - Identification of which WBS elements are decomposed to the work package level versus those decomposed only to a planning package level because future work detail is not yet known.
• 100% Rule Verification - Confirmation that the WBS captures 100% of the project scope — including project management work — with no duplication and no scope gaps between WBS elements.

How to Use This Work Breakdown Structure Template (PMBOK 8)

1. Apply the 100% rule rigorously - The WBS must capture 100% of the project scope — including project management deliverables. Any work not in the WBS is not authorized. Any work duplicated across WBS elements will be double-counted in cost and schedule estimates.
2. Decompose to a level that enables reliable estimation - The right level of decomposition is reached when each work package can be reliably estimated, assigned to a single accountable party, and tracked independently. Further decomposition creates unnecessary overhead; insufficient decomposition makes estimates unreliable.
3. Build the WBS collaboratively with the team - The team members who will perform the work have the most accurate knowledge of what the work involves. WBS development workshops produce more complete and credible decompositions than top-down analysis by the project manager alone.
4. Use the WBS to prevent scope creep - Any work not in the WBS is outside the approved scope. When stakeholders request additional work, require a change request that formally adds the work to the WBS before any effort is expended.
5. Pair the WBS with a WBS dictionary - The WBS provides structure; the WBS dictionary provides detail. Together they form the scope baseline. For complex projects, the WBS dictionary is essential for preventing misunderstandings about what is and is not included in each work package.
6. Align WBS elements with the schedule and cost baseline - WBS work packages should correspond one-to-one with schedule activities (or groups of activities) and cost accounts so that scope, schedule, and cost can be integrated in the performance measurement baseline.

When to Create This Document (PMBOK 8)

The WBS is created as an output of the Develop Scope Structure process, which is performed during the Planning Focus Area in PMBOK 8. WBS development begins after the Define Scope process produces the project scope statement and requirements documentation. The WBS must be completed and approved before the project schedule and cost estimates can be finalized, because both depend on the WBS as their organizing framework. In adaptive projects, an initial high-level WBS may be developed at project start and progressively elaborated as work is decomposed into epics and user stories in each planning iteration.

Related Templates

• WBS Dictionary Template
• Scope Baseline Template
• Scope Management Plan Template
• Project Schedule Template
• Resource Requirements Template

Complete Guide & Filled-In Example

Get the most out of this template with the two companion resources below:

• Work Breakdown Structure in PMBOK 8 - Complete Guide - Understand the purpose, key elements, and best practices before filling in the template.
• Download the Filled-In Example - Project Phoenix - See exactly how this document was completed for a real $72K website launch project.