A Work Breakdown Structure (WBS) is a tool used to define a project in discrete work elements in a Hierarchical format. It displays and defines the product, or products, to be developed and/or produced. It relates the elements of work to be accomplished to each other and to the end product. In other words, the WBS is an organized method to break down a product into subproducts at lower levels of detail. It’s used for planning, cost estimating, execution and control. Show
Purpose of the Work Breakdown Structure (WBS)The purpose of the WBS is to break down projects into manageable pieces, allowing for better planning, cost estimating, execution and control. Example of a Work Breakdown Structure (WBS)Why Develop a Work Breakdown Structure (WBS)The WBS is a means of organizing system development activities based on system and product decompositions. It is a product-oriented family tree composed of hardware, software, services, data, and facilities, which result from systems engineering efforts during the development and production of the system and its components, and which completely defines the program. The WBS is prepared from both the physical and system architectures and identifies all necessary products and services needed for the system. This top-down structure provides a continuity of flow down for all tasks. Enough levels must be provided to properly define work packages for cost and schedule control purposes. [1] The Benefits of a Work Breakdown Structure (WBS) are:
The Two Types of Work Breakdown Structures (WBS)The Program Manager (PM) is usually responsible for developing an overall program WBS and initiating the development of contract WBSs for each contract in accordance with common DoD practice established in Mil-HDBK 881. The two types of WBS on a program are:
Initial Work Breakdown Structure (WBS) DevelopmentWith the support of systems engineering, the PM develops the first three levels of the program WBS and provides contractors with guidance for lower-level WBS development. As with most standards and handbooks, the use of MIL-HDBK-881 cannot be specified as a contract requirement. Though WBS development is a systems engineering activity, it impacts costing, scheduling, budgeting professionals, and contracting officers. An integrated team representing these Stakeholders is needed to support WBS development. [1] Work Breakdown Structure (WBS) Guidance (MIL-STD-881)A WBS provides a consistent and visible framework for defense materiel items and contracts within a program. Mil-Standard 881D offers uniformity in definition and approach consistency for developing all WBS levels. Generating and applying uniform work breakdown structures improves communication in the acquisition process. It also provides direction to industry in extending contract work breakdown structures. [1] Standard: MIL-STD-881D “DoD Standard Practice WBS for Defense Materiel Items”Work Breakdown Structure (WBS) LevelsThe first three Work Breakdown Structure (WBS) Levels are organized as follows:
Example: WBS Levels How to Make a Work Breakdown Structure (WBS)The process of developing a WBS is straightforward but requires preparation and a clear understanding of what is required to be accomplished on a project.
How to Utilize a Work Breakdown Structure (WBS)A Work Breakdown Structure is primarily used as a planning tool to help the Program Manager and project personnel plan, define and organize a project into discreet deliverables. It describes all the work that needs to be accomplished to help avoid any confusion. There are three main components of a WBS that help with defining the program. These are:
Example: WBS Deliverable Levels Control Accounts in the Work Breakdown Structure (WBS)Control Accounts are WBS Elements at which the project plans to monitor and report performance. The Control Accounts can be any Element in the WBS. To assist with the monitoring and reporting, project management information tools are used to collect, analyze and report information at any Element within the WBS. Work Packages in the Work Breakdown Structure (WBS)Work Package (WP) is simply a task/activity or grouping of work and is the point at which work is planned, progress is measured, and earned value is computed. It can be translated into different terms in different companies and functions. It can be a design job, a tool design package, a build-to-package, a shop order, a part number, a purchase order, or any other definable task/activity at whatever level of control is normal for program management within the company. They normally represent the lowest level of a WBS. Work Packages ExampleWork packages come in a variety of formats, but the most common format is in the WBS. Below is a WBS, and the work packages are at the bottom level. Work Breakdown Structure (WBS) Application ToolsThere are a variety of application tools you can use in the development of a WBS. Below are some of the example types that can be used.
Contractor Work Breakdown Structure (WBS)The contract WBS is the Government – approved WBS for program reporting purposes and includes all program elements (for example, hardware, software, services, data, or facilities), which are the contractor’s responsibility. It includes the contractor’s discretionary extension to lower levels, in accordance with Government direction and the contract Statement of Work (SOW). Work Breakdown Structure (WBS) DictionaryThe WBS Dictionary is a document that describes each element work package in a project component of the WBS. These elements can include milestones, deliverables, activities, scope, resources, costs, and quality. The main purpose of the WBS dictionary is to define and communicate the work in more detail to help those working on an element or work package understand what needs to be done. AcqNotes TutorialsAcqLinks and References:Updated: 8/8/2022 Rank: G53.7 |