This article is about how to apply Work Breakdown Structures to engineering development and construction projects.<\/p>\n\n\n\n
To clarify the terms: the work breakdown structure is also called the project structure plan (PSP). Before the approach or method for creating a work breakdown structure is presented, here are a few points for general classification.<\/p>\n\n\n\n
It is a rule-based hierarchical representation of project goals, phases, product components and tasks or actions. A work breakdown structure is used in projects as an aid to structuring project content.<\/p>\n\n\n\n
A work breakdown structure is always required when a project takes on a scale and complexity that is no longer easy to survey. This is the case, for example, when many people are working on a project and there are dependencies between the work results. The WBS is the basic skeleton of the project and enables the project team and suppliers to have an objective view of the work steps required in a project or a project section.<\/p>\n\n\n\n
A work breakdown structure can have different levels of detail. This depends on the complexity of the respective sub-step. It may also be necessary to revise a WBS during the course of the project - i.e. expand, change or reduce it. If, for example, the product structure is worked out in a development process in the first phases of the project, it can only be included in the WBS later and the corresponding work steps assigned.<\/p>\n\n\n\n