I was recently involved in a virtual discussion on the Association for Project Management (APM - UK) website around the use and differences between a Product Breakdown Structure (PBS) and a Work Breakdown Structure (WBS). The resulting briefing document produced by the APM is summarised here[1] [1] with some additional commentary.
The concept of a WBS goes back to the development of PERT, in the USA, in the1950s (if not earlier) and is integral to the concept of Earned Value Management. The WBS is a hierarchal 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.
The concept of a PBS is integral to the PRINCE2 methodology. The origins of PRINCE can be traced back to the UK in the 1970s. The PBS is a hierarchical structure of things that the project will make or outcomes that it will deliver. It decomposes a "Main Project Product" into its constituent parts in the form of a hierarchical structure.
Whilst PBS and WBS look very similar, they serve different needs and both can have important roles to play in the project planning and control process and should not be confused.
What is a PBS?
The Product Breakdown Structure (PBS) is a hierarchical structure of things that the project will make or outcomes that it will deliver.
PBS generated by: P2ware Planner
The PBS diagram differentiates between the different types of product (ie, thing):
- The final product is the blue box at the top of screen;
- Assemblies are shown as green rhombus;
- Internal products (those built by the project) brown rectangles;
- External products (those either supplied by another project or bought in) are ovals;
Products are described using nouns or as an outcome described in the past tense (eg, ‘Test Plan’ or ‘Training Delivered’). The PBS is supported by a Product Log (list of products) and associated Product Descriptions that describe individual products in more detail. This enables quality expectations and responsibility for approval to be clearly identified at an early stage in the project life cycle.
Once completed the PBS gives confidence that the project team clearly understand what has to be created and that the relationship between a product and its constituent parts has been defined.
From the PBS a Product Flow Diagram can be produced to represent the order in which sub-products build into the main project product. This helps define the logic of the delivery plan.
To validate the PBS ask the following questions:
- Does the PBS contain work? If so this work needs either moving to the WBS or converting into a product.
- Are all high-level products broken down to an adequate level of detail?
- Have all external products been identified and sourcing confirmed? If they are outputs from other projects these represent risks that should go in the risks log and/or be defined as project interfaces/dependencies.
- Are all products couched as nouns or outcomes in the past tense?
What is a WBS?
The Work Breakdown Structure (WBS) provides a hierarchical structure of project activity; it focuses on the work required to accomplish the project. The WBS Dictionary is produced in conjunction with the WBS to store relevant detailed information in support of the planning process. In general the WBS makes it clear what work needs to be done and makes it easier for that work to be assigned to project teams[2] [2].
A typical WBS
Similar to the PBS, external work is included in the WBS with an internal manager taking responsibility for the oversight of the external contractor or supplier.
The completed WBS forms the basis of the Project Plan, it decomposes the main project into stages or major components, then into control-packages then into work-packages. The levels of detail are dependent upon the complexity of the project. Elements in a WBS are described by a verb and a noun (eg, ‘Install Servers’ or ‘Deliver Training’). The work-packages are then used as the basis for developing the project schedule, cost control and other management controls.
Once completed the WBS gives confidence that all of the work required to deliver the outcomes is understood. To validate the WBS ask the following questions:
- Does the WBS contain things? If so these things need to be moved to the PBS and each thing replaced in the WBS by a make thing work-package.
- Is there a work-package or combination of work-packages for all project products?
- Is work couched as nouns with associated verbs?
- Are all work-packages broken down into sufficient detail to be clear to the deliverer what is required?
- Are work-packages aligned to contracts where required?
Using the PBS and WBS to plan a project
The PBS should be developed first so that the project outcome is clearly understood and can be agreed with the sponsor. The PBS clarifies what is to be built or acquired. The Product Log is a useful place to record suppliers of external products and a Product Flow Diagram enables you to identify the order in which components of the product are required. This enables the logic of the overall plan to be understood at a high level before detailed planning begins.
A WBS can then be built to organise the construction of products as a set of work-packages. Organising the work into work-packages simplifies resource and team planning and provides the basis upon which a realistic project plan can be constructed. All elements of the PBS should be aligned to a phase boundary (Level 2 or 3 in the WBS) so that the project controls system can accurately measure progress in delivery.
Whilst there is no direct relationship between the structures of the WBS and the PBS, having a thing and a work related view of the overall project is very useful for validating the completeness of the plan. The key questions to ask are:
- Do you have products without work-packages? If so you will not be able to deliver the outcome or you have products in the PBS that in the cold light of day are not required.
- Do you work-packages without products? If so you are either doing unnecessary work or have missed something from the PBS.
Using the PBS and WBS to control a project
The PBS provides a useful management-tracking tool preventing phase (or stage) boundaries from being passed without tangible progress being made. In PRINCE2 the PBS (or more specifically the Product Log) also forms the basis of the quality assurance process. Ultimately it is the quality of each individual product that will drive the success of the project.
The WBS forms the basis of the detailed delivery plan and is used to task teams and individuals and hold them to account for their progress - this is the core concept in Earned Value Management[3] [3].
Conclusion
Used in conjunction the PBS and WBS offer powerful tools in ensuring the correctness and completeness of project plans, and then to ensure the project delivers everything required, and can really help the project manager establish clear communication and expectations with the wider stakeholder community and the project team. If you decide to use both, make sure the separate purposes and functions are respected.
However, it is quite common to see a hybrid WBS/PBS in a single chart (typically called a WBS) in this situation the separation between project phases, products and work packages tends to be based on the various ‘levels’ in the WBS. This is the approach adopted in MIL-STD-881C which forms the basis of all program WBSs developed for every acquisition made by the USA military.
Ultimately every work package should produces a product (even if some products are largely internal to the project) and every product requires work to be performed in its creation. The real difference between a WBS and a PBS is how the elements that combine to make up the completed project deliverable are described.
[1] [4] For more APM Web-Briefings see: https://www.apm.org.uk/web-briefings [5]
[2] [6] For more on developing and using a WBS see: http://www.mosaicprojects.com.au/WhitePapers/WP1011_WBS.pdf [7]
[3] [8] For more on Earned Value Management see: http://www.mosaicprojects.com.au/WhitePapers/WP1081_Earned_Value.pdf [9]