Work breakdown structure
A work-breakdown structure (WBS) in project management and systems engineering is a breakdown of a project into smaller components.
≈ 5 min read
Names in other languages
No names in other languages are held for this entry yet.
Article bodies are English and are not machine-translated. A name in another language is not a translation of the article.
A work-breakdown structure (WBS) in project management and systems engineering is a breakdown of a project into smaller components. It is a key project management element that organizes the team's work into manageable sections.
The Project Management Body of Knowledge defines the work-breakdown structure as 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." A WBS provides the necessary framework for detailed cost estimation and control while providing guidance for schedule development and control.
Types
PMI's Practice Standard for Work Breakdown Structures identifies two major types of work breakdown structures.
Deliverable-oriented WBS
Deliverable-oriented WBS, also known as Product breakdown structure uses key deliverables to group each work in the project.
Phase-oriented WBS
Phase-oriented WBS groups the work under key phases or stages of project lifecycle. The document has been revised several times. As of May 2023, the most recent revision is F, released 13 May 2022.
The version history and current revision of the standard are posted on the Defense Logistics Agency (DLA) ASSIST web site.It includes WBS definitions for specific defense materiel commodity systems and addresses WBS elements that are common to all systems. Defense Materiel Item categories from MIL-STD-881F are: Aircraft Systems Electronic/Generic Systems Missile/Ordnance Systems Strategic Missile Systems Sea Systems Space Systems Ground Vehicle Systems Unmanned Maritime Systems Launch Vehicle Systems Information Systems/Defense Business Systems The common elements identified in MIL-STD-881F, Appendix K are: Integration, assembly, test, and checkout; Systems engineering; Program management; System test and evaluation; Data; Peculiar support equipment; Common support equipment; Operational/Site activation; Contractor Logistics Support; Industrial facilities; Initial spares and repair parts.
The standard also includes additional common elements unique to Space Systems, Launch Vehicle Systems, and Strategic Missile Systems. In 1987, the Project Management Institute (PMI) documented expanding these techniques across non-defense organizations.
The Project Management Body of Knowledge (PMBOK) Guide provides an overview of the WBS concept, while the "Practice Standard for Work Breakdown Structures" is comparable to the DoD standard but is intended for more general application.
Plan outcomes, not actions
If the work breakdown structure designer attempts to capture any action-oriented details in the WBS, the designer will likely include either too many actions or too few actions. Too many actions will exceed 100% of the parent's scope, and too few will fall short of 100% of the parent's scope.
The best way to adhere to the 100% rule is to define WBS elements in terms of outcomes or results, not actions. This also ensures that the WBS is not overly prescriptive of methods, allowing for greater ingenuity and creative thinking on the part of the project participants.
When a project provides professional services, a common technique is to capture all planned deliverables to create a deliverable-oriented WBS. Work breakdown structures that subdivide work by project phases (e.g. preliminary design phase, critical design phase) must ensure that phases are clearly separated by a deliverable also used in defining entry and exit criteria (e.g., an approved preliminary or critical design review).
Product breakdown structure (PBS)
For new product development projects, the most common technique to ensure an outcome-oriented WBS is to use a product breakdown structure (PBS).
Feature-driven development
Feature-driven software projects may use a similar technique as the WBS, which is to use a feature breakdown structure.
Coding scheme
It is common for work breakdown structure elements to be numbered sequentially to reveal the hierarchical structure. The purpose of the numbering is to provide a consistent approach to identifying and managing the WBS across like systems regardless of vendor or service.
For example, 1.1.2 Propulsion (in the example below) identifies this item as a Level 3 WBS element, since there are three numbers separated by two decimal points. A coding scheme also helps WBS elements to be recognized in any written context, such as progress tracking, scheduling, or billing, and allows for mapping to the WBS Dictionary.
It is a preferred practice that the Statement of work or other contract descriptive include the same section terms and hierarchical structure as the WBS. A practical example of the WBS coding scheme is 1.0 Aircraft System 1.1 Air Vehicle 1.1.1 Airframe 1.1.1.1 Airframe Integration, Assembly, Test, and Checkout 1.1.1.2 Fuselage 1.1.1.3 Wing 1.1.1.4 Empennage 1.1.1.5 Nacelle 1.1.1.6 Other Airframe Components 1..n (Specify) 1.1.2 Propulsion 1.1.3 Vehicle Subsystems 1.1.4 Avionics 1.2 System Engineering 1.3 Program Management 1.4 System Test and Evaluation 1.5 Training 1.6 Data 1.7 Peculiar Support Equipment 1.8 Common Support Equipment 1.9 Operational/Site Activation 1.10 Industrial Facilities 1.11 Initial Spares and Repair Parts
References
[http://quicksearch.dla.mil/qsDocDetails.aspx?ident_number=36026 ASSIST entry for MIL-HDBK-881C Defense Acquisition University ACQ101 Summary for Work Breakdown Structures How to Make a Work Breakdown Structure NASA Work Breakdown Structure Handbook, NASA/SP-2010-3404, January 2010
Text derived from https://en.wikipedia.org/w/index.php?oldid=1361649699 under CC BY-SA 4.0; modifications have been made.
References
1 claim could not be tied to a specific sentence and is listed in the table below instead.