Building Effective Work Breakdown Structures (WBS)

Revision as of 11:29, 18 February 2023

"If you fail to plan, you are planning to fail" Benjamin Franklin

Regardless of the life cycle approach, successful project management requires a comprehensive and detailed plan ^[1]. A project manager’s main responsibilities include planning, integrating, and executing plans. Structured planning is essential given the relatively short duration and controlled resources of projects. Without proper planning, projects, and programs can face the following consequences ^[2]:

• No clear and defined requirements at the beginning of the project
• Setting unrealistic expectations
• Disorder and chaos
• Attempts to place blame
• Punishment

There are four main reasons for project planning: 1) To minimize or eradicate uncertainty, 2) To improve operational efficiency, 3) To gain a better understanding of the objectives, and 4) To establish the foundation for monitoring. The first major step in the planning process after defining the project requirements is to develop the Work Breakdown Structure (WBS), it is the most important element because provides a common framework for ^[2]:

• Describing the total project described as a summation of decomposed elements
• Planning can be performed
• Determining costs and budgets
• Monitoring time, cost, and performance
• Establishing schedules

Given all the benefits of building an effective WBS, the purpose of this article is to serve as a guide for project managers in:

1. Understanding the purpose and importance of creating a WBS.
2. Identifying the key characteristics and components of a WBS.
3. Implementing a delivered-oriented WBS effectively.
4. Evaluating the quality and completeness of a WBS.

Developed by Luisa Fernanda Salazar Rivera s222401

Introduction

Figure 1: Typical project launch ^[2]:

To determine when the development of a WBS can start, it is necessary to have an idea of the typical phases involved when launching a project. Figure 1 presents a standard project launch process:

The PMBOK Guide - Seventh Edition addresses the five elements related to scope ^{[1] [2]}:

• Scope: Scope encompasses all the deliverables required as part of a project. A deliverable is any unique product or work that should be produced to complete a process, phase, or project.
• Project Scope:Refers to the tasks that must be completed to achieve the defined scope of the project.
• Project Management: A systems approach to planning, scheduling, and controlling.
• Scope Statement:Document that describes the objectives, deliverables, end result, and justification of the project. It addresses the questions: who, what, when, why, where, how, and how many. This document confirms that the scope of the project aligns with the Statement of Work (SOW) provided by the customer.
• Scope Management Plan:Document that describes how the project scope will be defined, developed, monitored, controlled, and verified.
• Statement of Work (SOW):document that provides information related to the customer´s requirements and expectations for the project.

Having an understanding of key elements related to scope will enhance the reader´s comprehension of the following sections focused on detailed planning.

Overview of the WBS

What is a WBS

A WBS, as defined in the PMBOK Guide - Seventh Edition, is “A deliverable-oriented 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.” ^[1].

Core characteristics

Based on the definition of a WBS provided in section 2.1 the following characteristics should be highlighted ^{[1] [3]}:

• The deliverable orientation indicates the definition of specific outcomes of the project.
• The hierarchical representation indicates that a WBS is organized into parent-child relationships. Each descending level represents an increasingly detailed definition of the work.
• The decomposition nature indicates that a WBS translates the entire project scope into smaller components called work packages as will be further described in section 3.2. The 100% rule is related to this core characteristic of the WBS. This rule states that the WBS should contain 100% of the work defined in the project scope and include all the required deliverables that should be completed. This rule is applicable to all levels within the hierarchy in terms of having 100% of the activities defined at the "child" level to deliver the work presented by the “parent” level.

Purpose of creating a WBS

The purpose of having a WBS is to assist project managers and stakeholders to develop a clear vision of the project’s outcome. It provides a visual representation of all the deliverables across the project life cycle. Additionally, the WBS assists in the planning process by defining work packages that are more manageable pieces of work that can easily be scheduled, cost estimated, monitored, controlled, and communicated^[1].

Why is it essential

A well-defined WBS will aid in having a commonly accepted scope definition between all project functions and stakeholders. If this is not properly aligned, the chances of having inadequate and inaccurate project deliverables are high. Furthermore, these deliverables will prevent having a good understanding with stakeholders, and a good decision-making process, and will ultimately result in not achieving the project objectives. Therefore, it is essential to align expectations and have a common understanding of the project scope among all members and stakeholders ^{[1] [4]}.

Types and components of a WBS

Styles to present a WBS

The way project managers present the WBS can vary according to the organization's needs and how the WBS will be used. There are three main representations as shown in Table 1. It should be noted that Table 1 only introduces the most common representation styles. However, it is not a comprehensive WBS ^{[1] [5]}:

• Hierarchical:This is the most common representation of a WBS. Each box connects the child to the parent element in this structure. The most common version places the project at the top level and explicitly displays the hierarchical decomposition into smaller elements.

• Outline:In this style, the WBS is presented as a list. Each level displays an alphanumeric outline code or numbering scheme and the component.

• Tabular:Another representation is the tabular style. The columns in the table represent the hierarchical structure and each row has an alphanumeric outline code or numbering scheme and the component as in the outline style.

Table 1: WBS representation styles ^[5].

Hierarchical	Outline	Tabular

Types of decomposition for a WBS

There are different types of decompositions that can be used to build a WBS, including deliverable-oriented, phase-oriented, and product-oriented decompositions, among others. When building a WBS it is common to use a combination of different types of decompositions to ensure an effective WBS. To assist with practical implementation, some examples of elements that could be included in each type of decomposition are ^{[1] [5]}:

• Deliverable-oriented WBS: This type of decomposition breaks down the project into deliverables or outputs. Examples of elements could be manuals, prototypes, or software modules.
• Phase-oriented WBS: This type of decomposition breaks down the project into individual stages. Examples of elements could be planning, design, testing, and development.
• Product-oriented WBS: This type of decomposition breaks down the project into individual components of a product. Examples of elements could be suspension, brakes, electrical system, and interior.

Main WBS components

Figure 2: WBS example and components ^[1]

The focus of this section is to explain the main WBS components. This example was taken from the Practice Standard for Work Breakdown Structures by the Project Management Institute (PMI). Figure 3 was selected for simplicity in illustrating the product, and the intention is to allow the reader to focus on the WBS and its essential components. ^{[1] [5]}. The main components of a WBS will be explained using figure 1 as a reference:

• Levels and WBS IDS:

Level 1: Regardless of the type of decomposition or the style of the WBS, the first level always represents the name of the project, product, or initiative. This level includes the entire scope of work necessary to produce the product, service, or outcome of the project designated by the number 1. In figure 2, the “bicycle” represents the product of the project.

Level 2: This is the first level of decomposition for the project which provides a high-level view of the scope of the project. The numbering in the second level is 1.1, 1.2, 1.3,…., 1,n. In the example of the bicycle, the second level represents all the components required to deliver the final product.

Level 3 and below: These levels decompose further the deliverables from Level 2. These levels correspond to only one parent in level 2 and the numbering is: 1.1.1, 1.1.2, 1.1.3, …, 1.1.n, 1.2.1, 1.2.2, 1.2.3, …, 1.2.n, according to the needs of the project.

• Work Packages:

As introduced in section 1.1, a work package is defined as the lowest level in a WBS which represent tasks that can be assigned to a team member or department. For project managers, this level of detail will allow to reliably estimate cost, and duration, and to monitor and control the work ^{[1] [5]}.

Building effective WBS

Preparation methods

There are different methods and tools available to create a WBS such as top-down and bottom-up development strategies, WBS organizational standards, WBS templates, brainstorming, expert assistance, and mind mapping, among others. The selected method depends on the project objectives, requirements, assumptions, and constraints ^[5]. This article will focus on explaining the top-down and bottom-up approaches as they are often referred to in the literature about WBS.

Top-down method

Figure 2: Top-down approach ^[5].

This is one of the most preferred methods when creating a WBS. The decomposition process starts at the top of the WBS. In other words, you begin with the overall picture and continue breaking down the work into smaller, more manageable components ^{[1] [5]}. The following steps describe the general approach for developing a WBS following the top-down method:

Step 1: Identify all the final products, services, or outcomes that the project will deliver. They are the level 2 components.

Step 2: Define major interim deliverables to accomplish each level 2 components.

Step 3:Break down each major deliverable to a level of detail that allows appropriate management and control. Following the 100% rule, the total of elements at each level represents 100% of the necessary work for the above element.

Step 4:Review and validate with key stakeholders until agreed that the project planning can be successfully completed and that the execution will produce the required deliverables and results.

Bottom-up method

Figure 3: Bottom-up approach ^[5].

This method starts at the lowest level of deliverables – the work packages – and works upwards to the top level of the WBS ^{[1] [5]}. The following steps describe the general approach for developing a WBS following the bottom method:

Step 1: Identify all the work packages of the project (deliverables), each work package typically contains one deliverable

Step 2:Group related work packages logically

Step 3:Aggregate deliverables to the next parent level. Following the 100% rule, the sum of elements at each level represents 100% of the work required below it

Step 4:Once a specific set of interconnected work packages has been consolidated into a parent element, re-examine the subset to make sure that all the work has been included

Step 5:Repeat until all the work packages have been aggregated to a single parent, level 1 element of the WBS, and make sure that the completed structure encompasses the entire scope.

Step 6:Review and validate with key stakeholders until agreed that the project planning can be successfully completed and that the execution will produce the required deliverables and results

Decomposing the project work

How to decompose the project work?

Figure 4: Decomposition technique diagram ^[5].

The decomposition technique is used when creating a WBS to break down the project. This is an iterative process that starts by identifying the best approach, according to section 3.2, to decompose the major deliverables. Figure 5 shows the iterative nature of the work decomposition until all the work packages are identified. When breaking down the scope of the project, you should consider the question: Is this work package detailed enough to be effectively estimated and managed, or should it be broken down further for better comprehension and management? ^[5].

When to stop decomposing the work?

Various guidelines for determining when to stop the decomposition process are based on the amount of time that takes to complete a work package ^[5]. An example of this rule is given by Dr. Harold Kerzner: "A typical work package may be 200–300 hours and approximately two weeks in duration"^[2]. A practical tip given by Liliana Buchtik is to decompose to the level of detail for which you are able to manage, assign the work, and estimate cost and time ^[5].

WBS Dictionary

The WBS dictionary is a document that supports the WBS by providing comprehensive information for each element within it. The information in the WBS dictionary typically includes a detailed description of the work, deliverables, and milestones associated with each activity. The dictionary components can be used to drive scheduling, cost estimating, managing, and controlling work ^[1]. Figure 6 provides a description of each component in the WBS dictionary and an example based on figure 3.

• Some of the methods recommended by the PMI for cost estimate include expert judgement, analogous estimating, parametric estimating, and three-point estimating. However, those topics will not be covered in this article.

Steps for building an effective WBS

The following steps are presented as a guide for building a valuable WBS ^[5].:

Step 1: Obtain inputs. Including the Scope Management Plan and the Preliminary Scope Statement.

Step 2: Define the team. Including relevant stakeholders, team members, experts, colleagues, and project sponsor.

Step 3: Analyze the scope. Identify and analyze the work required to accomplish the scope of the project.

Step 4: Determine the decomposition approach8. Either deliverable-oriented, phase-oriented, or product-oriented as described in section 3.2.

Step 5: Determine the representation style such as hierarchical, outline, or tabular8 as described in section 3.1.

Step 6: Determine software to create the WBS. Popular useful tools include WBS Schedule PRO, Trello, and Asana.

Step 7: Determine the preparation method approach and apply the decomposition technique. As outlined in section 4.1 select the preparation method, either top-down or bottom-up, and follow the corresponding steps. Then, apply the decomposition technique diagram presented in figure XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX.

Step 8:Apply the 100% rule to verify that all the required work is included and ensure no duplicates or overlaps in work.

Step 9:Check the level of decomposition. Verify that the work packages are decomposed to an appropriate level. Section 4.2.2 addressed when you should stop decomposing

Step 10:Assign WBS IDS. Assign a WBS to each component following the description presented in section 3.3.

Step 11:Insert level legend8. If the levels have been identified with a color, as depicted in figure XXXXXX, use a legend to identify each level.

Step 12:Obtain stakeholder input. Engage in a dialogue with your project team and stakeholders to initiate a series of updates and modifications until reaching an agreement with all the relevant stakeholders.

Step 13:Create WBS dictionary as presented in section 4.3 simultaneously with step 12.

Step 14:Obtain approval and communicate. After approval, if changes are necessary, go through the formal change control process. Present the finished WBS and WBS dictionary to the project team and stakeholders.

Step 15:Generate the scope baseline. As presented in figure 1, with the project scope statement, the WBS, and the WBS dictionary, the scope baseline can be generated. Going forward, any request for changed to the scope should be assessed against the scope baseline.

Evaluating the quality of a WBS

The PMI Practice Standard for WBS defines core quality characteristics that a WBS must fulfill to be considered of high quality ^{[5] [6]}

Quality Principle 1

"A quality WBS is a WBS constructed in such a way that it satisfies all of the requirements for its use in a project" ^[6] There are two sub-principles associated:

WBS Quality Sub-Principle 1: Core Characteristics

There is a set of core characteristics essential for creating a valuable WBS, including ^[6]:

• It is deliverable oriented

• Defines the scope of the project

• Clarifies and communicates the work for stakeholders

• Follows the 100% rule

• Captures all the deliverables, including project management

• The level of decomposition contains 100% of the work required in the parent level

• Work packages support the identification of the tasks required to deliver the work packages

• It is a hierarchical structure

• It is a graphical representation of the scope in a hierarchical, outline, or tabular style

• Elements are defined using nouns

• Numbering scheme aids in identifying its hierarchical nature

• Has at least two levels with at least one level of decomposition

• Created by those performing the project in collaboration with stakeholders and experts

• Iteratively evolves with the progressive elaboration of the project scope until the scope has been baselined

• Updated according to project change control

WBS Quality Sub-Principle 2: Use-related Characteristics

These characteristics may differ from one WBS to another and intend to be used for purposes unique to a specific project. Including ^[6]:

• Decomposed to the appropriate level

• Provides detailed information for communicating all the work

• Allow monitoring and controlling activities

• Enables assignment for accountability

• Has a clear and organized structure to meet the project management requirements.

Limitations

References

1. ↑ ^{1.00 1.01 1.02 1.03 1.04 1.05 1.06 1.07 1.08 1.09 1.10 1.11 1.12 1.13} Project Management Institute, Inc. (PMI)., "Practice Standard for Work Breakdown Structures (3rd Ed.)", 2019
2. ↑ ^{2.0 2.1 2.2 2.3 2.4} Kerzner, H. ., "Project Management: A Systems Approach to Planning, Scheduling, and Controlling. (7th Ed.) ", 2009
3. ↑ Norman, E; Brotherton, S; Fried, R. "Work Breakdown Structures: The Foundation for Project Management Excellence. ", 2008
4. ↑ Cicala, G. "The Project Managers Guide to Microsoft Project 2019: Covers Standard, Professional, Server, Project Web App, and Office 365 Version", 2019
5. ↑ ^{5.00 5.01 5.02 5.03 5.04 5.05 5.06 5.07 5.08 5.09 5.10 5.11 5.12 5.13 5.14 5.15} Bucktik, L."Secrets to Mastering the WBS in Real-World Projects: The Most Practical Approach to Work Breakdown Structures (WBS)! (2nd Ed.) PMI ", 2010
6. ↑ ^{6.0 6.1 6.2 6.3} Project Management Institute, Inc. (PMI)., "Practice Standard for Work Breakdown Structures (2nd Ed.)", 2013

References explanations