Work break down structure (WBS)

Abstract

Taking on a project can be a confusing task for even the most experienced project manager. In the start-up phase of a project the goal is defined, and it is expected to estimate a budged and a timeframe of the project. Often several things will happen doing the elapse of the project, that in the end will lead up to the final reaching of the project goal or scope. To create a better view of the project it can be helpful to part the project and the goal onto sub-goals or sub-events – to break down the project. By estimating the timeframe and budget of the sub-events or sub-goals, the timeframe of the project can be estimated as well as the budged. This method is referred to as Work Break down Structure (WBS), as it is a way to structure the project by breaking it down. This is the addressed subject of this article.

The article consist of the following sections:

- What is WBS?

- Why is WBS an important tool in project management?

- How to implement WBS

- What are the limitations of WBS?

In each section, the question will be answered.

This article is a part of the final deliverable in the course 42433 Advanced engineering project, program and portfolio management taught in the spring of 2022 on DTU. It is written by a student for other students taking the same course.

What is WBS?

A work breakdown structure is defined by the ISO Standard 21502 as "decomposition of the defined scope of a project or programme into progressively lower levels consisting of elements of work" [ref]. In other words: when the scope of a project or programme is defined in the very beginning of this project- or programmes lifespan, it might be favourable to look at the work that is needed in order to fullfill the scope and deliver on the project/programme.

Why is WBS an important tool in project management?

The work breakdown structure is an important tool for a project manager when estimating a time schedule and budget of a project. When breaking down the work into smaller projects or workpages a overview of the project is created. It gives the project manager the ability to analyse the needs of a workpages in terms of workload, resurses needed, risks linked to the specific work and preperations needed to fullfill a surtain work. The workpages or smaller projects can be scheduled in a model such as ... fiskeben, vandfald, andre modeller. This is infact what makes the breakdown structure a great tool, as the a overview of the hole project is secured and estimated. Also this way of scheduleing the work in smaller workpages makes it easier for the projectmanager to watch out for delays on surtain areas of the project, inform the different stakeholders and handle the work-, risk- and resucse-flow as the project proceeds.

How to implement WBS

The Work breakdown structure should be implemented in the planning of the execution of a project. To what extent the work should be broken down and the level of details planed in every workpage or sub-project depends on the size of the project.

What are the limitations of WBS?

As a project manager it is important to know what you dont know - and to expect the unexpected. A work breakdown structure of a project might give a great overview of a project but as much as this scheduleing of the smaller workpages provides a sound estimation of the project, everything can still go wrong. The overview provides a better opportunity to do risk analysis on the project, and

keep track of afvigelser and act on them - se the the project plan as a work in progress and not a finished product.

Links/ref CBS link: https://www.adeaca.com/blog/faq-items/what-is-a-work-breakdown-structure/ course notes complexity https://learn.inside.dtu.dk/d2l/le/content/102752/viewContent/401279/View [X]Figure 1: Picture of tree schedule, Author: WorkBreakdownStructure.com, Webside: https://www.workbreakdownstructure.com/ [Y]Figure 2: Picture of Gantt Chart, Author: Roger Duke, Webside: https://www.gantt.com/