Building Effective Work Breakdown Structures (WBS)
(→Introduction) |
(→Overview of the WBS) |
||
| Line 40: | Line 40: | ||
Having an understanding of key elements related to scope will enhance the reader´s comprehension of the following sections focused on detailed planning. | 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 == | + | ==2 Overview of the WBS == |
| − | === What is a WBS === | + | ===2.1 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.” <ref name="WBS Standard"> Project Management Institute, Inc. (PMI)., ''"Practice Standard for Work Breakdown Structures (3rd Ed.)"'', 2019</ref>. | 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.” <ref name="WBS Standard"> Project Management Institute, Inc. (PMI)., ''"Practice Standard for Work Breakdown Structures (3rd Ed.)"'', 2019</ref>. | ||
| − | === Core characteristics === | + | ===2.2 Core characteristics === |
| − | === Purpose of creating a WBS === | + | |
| − | === Why is it essential === | + | ===2.3 Purpose of creating a WBS === |
| + | ===2.4 Why is it essential === | ||
== Types and components of a WBS == | == Types and components of a WBS == | ||
Revision as of 18:26, 12 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 [2]. 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:
- Understanding the purpose and importance of creating a WBS.
- Identifying the key characteristics and components of a WBS.
- Implementing a delivered-oriented WBS effectively.
- Evaluating the quality and completeness of a WBS.
Developed by Luisa Fernanda Salazar Rivera s222401
Contents |
1 Introduction
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 [2]. Figure 1 presents a standard project launch process:
The PMBOK Guide - Seventh Edition addresses the five elements related to scope:
- 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. [1] [2].
- Project Scope:Refers to the tasks that must be completed to achieve the defined scope of the project [1] [2].
- 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 [1] [2].
- Scope Management Plan:Document that describes how the project scope will be defined, developed, monitored, controlled, and verified. [1] [2].
- Statement of Work (SOW):document that provides information related to the customer´s requirements and expectations for the project [1] [2].
Having an understanding of key elements related to scope will enhance the reader´s comprehension of the following sections focused on detailed planning.
2 Overview of the WBS
2.1 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].
2.2 Core characteristics
2.3 Purpose of creating a WBS
2.4 Why is it essential
Types and components of a WBS
Styles to present a WBS
Types of decomposition for a WBS
Main components
Building effective WBS
Preparation methods
Top-down method
Bottom-up method
Decomposing the project work
How to decompose the project work?
When to stop decomposing the work?
WBS Dictionary
Steps for building an effective WBS
Evaluating the quality of a WBS
Quality Principle 1
WBS Quality Sub-Principle 1: Core Characteristics
Limitations
References
- ↑ 1.0 1.1 1.2 1.3 1.4 1.5 1.6 Project Management Institute, Inc. (PMI)., "Practice Standard for Work Breakdown Structures (3rd Ed.)", 2019
- ↑ 2.0 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9 Kerzner, H. ., "Project Management: A Systems Approach to Planning, Scheduling, and Controlling. (7th Ed.) ", 2009
