Which document describes the projects deliverables and the work required to create those deliverables?

Breaking work into smaller tasks is a common productivity technique used to make the work more manageable and approachable. For projects, the Work Breakdown Structure (WBS) is the tool that utilizes this technique and is one of the most important project management documents. It singlehandedly integrates scope, cost and schedule baselines ensuring that project plans are in alignment.

The Project Management Institute (PMI) Project Management Book of Knowledge (PMBOK) defines the Work Breakdown Structure as a “deliverable oriented hierarchical decomposition of the work to be executed by the project team.” There are two types of WBS: 1) and 2) . The most common and preferred approach is the Deliverable-Based approach. The main difference between the two approaches are the Elements identified in the first Level of the WBS.

Deliverable-Based Work Breakdown Structure

A Deliverable-Based Work Breakdown Structure clearly demonstrates the relationship between the project deliverables (i.e., products, services or results) and the scope (i.e., work to be executed). Figure 1 is an example of a Deliverable-Based WBS for building a house. Figure 2 is an example of a Phase-Based WBS for the same project.

Figure 1 – Deliverable Based Work Breakdown Structure

In Figure 1, the Level 1 Elements are summary deliverable descriptions. The Level 2 Elements in each Leg of the WBS are all the unique deliverables required to create the respective Level 1 deliverable.

Phase-Based Work Breakdown Structure

In Figure 2, a Phase-Based WBS, the Level 1 has five Elements. Each of these Elements are typical phases of a project. The Level 2 Elements are the unique deliverables in each phase. Regardless of the type of WBS, the lower Level Elements are all deliverables. Notice that Elements in different Legs have the same name. A Phase-Based WBS requires work associated with multiple elements be divided into the work unique to each Level 1 Element. A WBS Dictionary is created to describe the work in each Element.

Figure 2 - Phase Based Work Breakdown Structure

A good WBS is simply one that makes the project more manageable. Every project is different; every project manager is different and every WBS is different. So, the right WBS is the one that best answers the question, “What structure makes the project more manageable?”.

How to Make a Work Breakdown Structure

A good Work Breakdown Structure is created using an iterative process by following these steps and meeting these guidelines:

1. Gather Critical Documents
   1. Gather critical project documents.
   2. Identify content containing project deliverables, such as the Project Charter, Scope Statement and Project Management Plan (PMP) subsidiary plans.
2. Identify Key Team Members
   1. Identify the appropriate project team members.
   2. Analyze the documents and identify the deliverables.
3. Define Level 1 Elements
   1. Define the Level 1 Elements. Level 1 Elements are summary deliverable descriptions that must capture 100% of the project scope.
   2. Verify 100% of scope is captured. This requirement is commonly referred to as the 100% Rule.
4. Decompose (Breakdown) Elements
   1. Begin the process of breaking the Level 1 deliverables into unique lower Level deliverables. This “breaking down” technique is called Decomposition.
   2. Continue breaking down the work until the work covered in each Element is managed by a single individual or organization. Ensure that all Elements are mutually exclusive.
   3. Ask the question, would any additional decomposition make the project more manageable? If the answer is “no”, the WBS is done.
5. Create WBS Dictionary
   1. Define the content of the WBS Dictionary. The WBS Dictionary is a narrative description of the work covered in each Element in the WBS. The lowest Level Elements in the WBS are called Work Packages.
   2. Create the WBS Dictionary descriptions at the Level with detail enough to ensure that 100% of the project scope is covered. The descriptions should include information such as, boundaries, milestones, risks, owner, costs, etc.
6. Create Gantt Chart Schedule
   1. Decompose the Work Packages to activities as appropriate.
   2. Export or enter the Work Breakdown Structure into a Gantt chart for further scheduling and project tracking.

Caution: It is possible to break the work down too much. How much is too much? Since cost and schedule data collection, analysis and reporting are connected to the WBS, a very detailed WBS could require a significant amount of unnecessary effort to manage.

There are many WBS software tools available. Some of them are based on mind mapping and others are drawing tools. You can read about these tools in this WBS software review.

Here is an example of how to make a WBS with MindView:

How to Use a Work Breakdown Structure

The Work Breakdown Structure is used for many different things. Initially, it serves as a planning tool to help the project team plan, define and organize scope with deliverables. The WBS is also used as the primary source of schedule and cost estimate activities. But, its biggest contributions to a project are is use as a description all of the work and as a monitoring and controlling tool.

Which document describes the project deliverables and the work required to create the deliverables?

What is project scope document?

What is project scope statement?

What is a scope statement example?