(WBS) - Work Breakdown Structure
The WBS (work breakdown structure) is a process used in project management to identify the scope of a project and all the associated tasks that must be done to complete the project as defined. For this purpose, a results-oriented hierarchical decomposition of the work is carried out. This technology not only makes the work more accessible and manageable. It also enables the monitoring of different processes of a project, the estimation of costs and schedules and helps with team building. This led to WBS becoming one of the most important project management tools.
In the following, the author presents the different structuring techniques of a work breakdown structure. Furthermore, he describes the process of creating a work breakdown structure, the different forms of presentation as well as the advantages and limitations of a work breakdown structure and will illustrate these with examples
Contents |
Backgroud
As part of the U.S. Navy's fleet ballistic missile program (Polaris), the Program Evaluation and Review Technique (PERT) program was established in 1957 to address backlogs in planning. The program was designed to find a solution that would generate all the necessary tasks and efforts for the project based on its outcome. In 1962, the Department of Defense (DOD) and NASA published the first description of the work breakdown structure (WBS) with PERT as a model and later adopted it as the standard for the entire DOD product line. However, the first naming took place only in 1968. Beginning in 1987, the work breakdown structure (WBS) was first introduced by the Project Management Institute (PMI) with the PMBOK as a standard procedure for non-military operations, e.g., for applications in companies and other organizations and has been further developed by means of the introduction of a project charter since 1999. [1]
WBS in Project Management
A project is characterized by being temporary and providing a unique product, service or result. As each project in its entirety has never been done before, it involves a certain degree of uncertainty and risk. To counteract this, it is important that a project is planned comprehensively. This planning includes costs, resources, schedule, risks and the project scope with its specifically defined goals, objectives and deliverables. The WBS helps the planning team reduce the extent of uncertainty by breaking down the entire scope of the project into a series of smaller components making it more manageable and less overwhelming. [2] [3]
According to PMI, a WBS is defined as follows: "The WBS is a 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. The WBS organizes and defines the total scope of the project and represents the work specified in the current approved project scope statement".[4] The WBS is used to explicitly describe the project scope, the deliverables and the outcome of a project. It answers the question of the "what ?" of the project. The processes that lead to the results, the "how ?", as well as the schedule witch determines the exact time of the production of a deliverable, the "when ?", are not answered by using a WBS. [5]
-important communication mechanism that assists in understanding and communication the scope of work, createating a common language among all Stakeholdes involved.
-assists in verifying consistency and completeness of scope and avoiding duplication
-communication is one of the project management disciplines with the highest impact on project success -provides the framework and serves as basis for for defining activity processes estimate costs and resources and identifing risks, the plan quality process -WBS establish the framework for planning, controlling, executing and the projects work
Fundamentals of the WBS
- Packages
- Control accounts
- Levels & coding
- WBS Dictionary
- 100% Rule
WBS Structure
- MECE Structure
Representation of WBS
- WBS List
- WBS Tree Diagram
- Gantt Chart
Phase-Based WBS
- Build around the project life cycle phases
How to Create a Work Breakdown
- Top-down
- Bottom-up
- Yo-Yo approach
Benefits and limitation of WBS
Benefits
- Detailed illustration of scope
- Monitor progress
- Cost and schedule estimates
- Build project teams
Limitation
[1] [4] [6] [7] [5] [2] [8] [9] [3]
References
- ↑ 1.0 1.1 Eby, K (2016) Getting Started with Work Breakdown Structures (WBS) - https://www.smartsheet.com/getting-started-work-breakdown-structures-wbs
- ↑ 2.0 2.1 Project Management Institute, Inc (2019) Practice standard for work breakdown structures – Third edition, Newtown Square, Pennsylvania: Project Management Institute, Inc
- ↑ 3.0 3.1 Burek, P. (2013) The ABC basics of the WBS Paul Burek - Paper presented at PMI® Global Congress 2013—North America, New Orleans, LA. Newtown Square, PA: Project Management Institute
- ↑ 4.0 4.1 Project Management Institute, Inc (2017) A Guide to the PROJECT MANAGEMENT BODY OF KNOWLEDGE – Sixth edition, [direct quote p. 157], Newtown Square, Pennsylvania: Project Management Institute, Inc
- ↑ 5.0 5.1 Norman, S; Brotherton, S and Fried, R (2008) Work Breakdown Structures: The foundation for project management excellence – New Jersey: John Wiley & Sons, Inc
- ↑ Lester, E (2017) Chapter 12 - Work Breakdown Structures in Project Management, Planning and Control – Seventh edition, Oxford: Elsevier Butterworth-Heinemann, pages 53-59,
- ↑ Swiderski, M (n.d.) Work Breakdown Structures (WBS) - https://www.workbreakdownstructure.com/
- ↑ Burghate, M (2018) Work Breakdown Structure: Simplifying Project Management – Vol. 3, No. 2, International Journal of Commerce and Management Studies (IJCAMS)
- ↑ Organ, Christine (2022) How To Use Work Breakdown Structure As A Project Management Tool - https://www.nasdaq.com/articles/how-to-use-work-breakdown-structure-as-a-project-management-tool
