Skip to main content

Work Breakdown Structure (WBS)

A Work Breakdown Structure (WBS) is a methodical way of decomposing the project work into meaningful and logical smaller pieces for the purpose of planning and control. When completed the WBS should include all activities associated with the project scope.

It becomes the data dictionary for communicating on the project. Work Breakdown Structures have a child / parent relationship which means that it's possible to roll up and summarize any information from the lower levels and upwards. This is true for activity cost, resource effort and schedule information.

It can also be used to assign responsibility for groups of activities to different functional managers for planning and or accountability purposes.

It should also be used as the format for capturing and outlining changes to the project. One way of representing the WBS is to outline the format similar to a “Table of Contents” in a book.

An example could be:

Another way is to outline the format like a tree structure similar to a Company’s Organizational Chart. 

In any case, the lowest level is known as a work package, which would be made up of a number of activities or tasks with clear resource assignments and functional responsibility assigned. 

There is no limits to the level of detail one can go down to, nor there's a need to have the same number of levels for each branch. 

However there should be guidelines to assure the desired level:
• assign responsibility of definition and completion for accountability purposes. 
• estimate the required resources and their required hours/days of performance. 
• estimate the duration (elapsed time) between start and finish of the element. 
• identify logical predecessor and successors to the element. 
• short enough so that it's possible to define its doneness criteria for control and progress capturing purposes.

Note: The more detail one creates the more time and effort is required to maintain the WBS. One has to decide on the trade off between more control (i.e. detail) and overhead (i.e. amount of data to update).

There are many approaches to breaking down the work into smaller packages. Since the data can be rolled up and summarized into different levels, the approach one initially takes will decide on what kind of information it will be able to report on. Based on one's reporting requirements and type of project, it's possible to mix and match formats at different levels.

Popular posts from this blog

The differences between Project, Operation and Program

We said that a project is defined as a temporary endeavor that consumes resources, incurs cost and produce deliverables over a finite period of time to achieve a specific goal. They come in all shapes and sizes and can vary in length or complexity.

Operation type activities are similar to project activities in that they too produce deliverables, consume resources and incur cost. However they are on-going or repetitive in nature, hence they are not project activities or tasks. Some examples of operation activities are weekly maintenance of databases, paying invoices or help desk operations activities.

Programs are much larger than projects. They are made up of many projects and on going activities such as operation type activities and are similar to projects as they consume resources, incur cost and produce deliverables. However programs are more complex and include repetitive operation type activities such as maintenance work, facility administration etc, and are funded typically on a…

Forecasting Project Costs using Variance Analysis

One way to report on cost control and forecasting during project execution is to use the Variance Analysis method, that is, explaining the difference (or variance) between actual costs and the budgeted costs with numbers and make new estimates for completing the work. Please consult this link Earned Value Management for related literature and references.
For the purpose of making these calculations, I will use an hypothetical project example (but it could also be a task or phase). "A company has contracted a service provider to deliver a project in 10 working days (80 hours) for the estimated cost of $10,000 and a work effort of 200 hours. The contract is Time and Material, this means that the company pays the provider for the number of hours actually required to perform the service. So, the provider has no incentive to minimize the number of hours expended on the service. The less efficient the provider is, the more money it makes!"
Summary of Time and Material Contract (re…

Using PERT for estimating tasks

A simple way for estimating tasks is to use the PERT (Program Evaluation review technique) weighted average method. This method uses a weighted average duration estimate to calculate task duration, it gives the opportunity to take into account information based on different types of estimates values (such as poorly defined areas, probabilistics, and ranges for the schedule). This method is based on the Beta distribution model because it can model events which are constrained to take place within an interval defined by a minimum and maximum value. (For this reason, the Beta distribution is used extensively in PERT, CPM and other project planning/control systems to describe the time to completion of a task).

The term weighted average means that the equation uses weighted factors to calculate the expected task duration.
The equation and process modelling a task for PERT is the following:  E=(O+4M+P)/6 (equation)  E= Expected Value  O= Optimistic Value (this is equivalent to a minimum val…