Work Breakdown Structure

Work Breakdown
Structure
www.AssignmentPoint.com
A work breakdown structure (WBS), in project management and systems
engineering, is a deliverable-oriented decomposition of a project into smaller
components. A work breakdown structure is a key project deliverable that
organizes the team's work into manageable sections. The Project Management
Body of Knowledge (PMBOK) defines the work breakdown structure as a
"deliverable oriented hierarchical decomposition of the work to be executed by
the project team."
A work breakdown structure element may be a product, data, service, or any

combination thereof. A WBS also provides the necessary framework for
detailed cost estimating and control along with providing guidance for schedule
development and control.
Overview
WBS is a hierarchical and incremental decomposition of the project into phases,

deliverables and work packages. It is a tree structure, which shows a subdivision
of effort required to achieve an objective; for example a program, project, and
contract. In a project or contract, the WBS is developed by starting with the end
objective and successively subdividing it into manageable components in terms
of size, duration, and responsibility (e.g., systems, subsystems, components,
tasks, subtasks, and work packages) which include all steps necessary to
achieve the objective.
The work breakdown structure provides a common framework for the natural
development of the overall planning and control of a contract and is the basis
for dividing work into definable increments from which the statement of work
can be developed and technical, schedule, cost, and labor hour reporting can be
established.
A work breakdown structure permits summing of subordinate costs for tasks,

materials, etc., into their successively higher level “parent” tasks, materials, etc.
For each element of the work breakdown structure, a description of the task to
be performed is generated. This technique (sometimes called a system
breakdown structure) is used to define and organize the total scope of a project.
The WBS is organized around the primary products of the project (or planned
outcomes) instead of the work needed to produce the products (planned
actions). Since the planned outcomes are the desired ends of the project, they
form a relatively stable set of categories in which the costs of the planned
actions needed to achieve them can be collected. A well-designed WBS makes
it easy to assign each project activity to one and only one terminal element of
the WBS. In addition to its function in cost accounting, the WBS also helps map
requirements from one level of system specification to another, for example a
requirements cross reference matrix mapping functional requirements to high
level or low level design documents.
The development of the WBS normally occurs at the start of a project and
precedes detailed project and task planning.
History
The concept of work breakdown structure developed with the Program
Evaluation and Review Technique (PERT) by the United States Department of
Defense (DoD). PERT was introduced by the U.S. Navy in 1957 to support the
development of its Polaris missile program. While the term "work breakdown
structure" was not used, this first implementation of PERT did organize the
tasks into product-oriented categories.
By June 1962, DoD, NASA and the aerospace industry published a document
for the PERT/COST system which described the WBS approach. This guide
was endorsed by the Secretary of Defense for adoption by all services. In 1968,
the DoD issued "Work Breakdown Structures for Defense Materiel Items"
(MIL-STD-881), a military standard requiring the use of work breakdown
structures across the DoD.
The document has been revised several times, most recently in 2011. The
current version of this document can be found in "Work Breakdown Structures
for Defense Materiel Items" (MIL-STD-881C). 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-881C are:
 Aircraft Systems WBS
 Electronic Systems WBS
 Missile Systems WBS
 Ordnance Systems WBS
 Sea Systems WBS
 Space Systems WBS
 Surface Vehicle Systems WBS
 Unmanned Air Vehicle Systems WBS
 Unmanned Maritime Systems WBS
 Launch Vehicle Systems WBS
 Automated Information Systems WBS
The common elements identified in MIL-STD-881C, Appendix L are:

Integration, assembly, test, and checkout; Systems engineering; Program
management; System test and evaluation; Training; Data; Peculiar support
equipment; Common support equipment; Operational/Site activation; Industrial
facilities; Initial spares and repair parts. The standard also includes additional
common elements unique to Space Systems, Launch Vehicle Systems and
Automated Information Systems.
In 1987, the Project Management Institute (PMI) documented the expansion of

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 handbook, but is intended for more general application.
Design principles
100% rule
An important design principle for work breakdown structures is called the 100%
rule. It has been defined as follows:
The 100% rule states that the WBS includes 100% of the work defined by the
project scope and captures all deliverables – internal, external, interim – in
terms of the work to be completed, including project management. The 100%
rule is one of the most important principles guiding the development,
decomposition and evaluation of the WBS. The rule applies at all levels within
the hierarchy: the sum of the work at the “child” level must equal 100% of the
work represented by the “parent” and the WBS should not include any work
that falls outside the actual scope of the project, that is, it cannot include more
than 100% of the work… It is important to remember that the 100% rule also
applies to the activity level. The work represented by the activities in each work
package must add up to 100% of the work necessary to complete the work
package.
Mutually exclusive elements
Mutually exclusive: In addition to the 100% rule, it is important that there is no

overlap in scope definition between different elements of a work breakdown
structure. This ambiguity could result in duplicated work or miscommunications
about responsibility and authority. Such overlap could also cause confusion
regarding project cost accounting. If the WBS element names are ambiguous, a
WBS dictionary can help clarify the distinctions between WBS elements. The
WBS Dictionary describes each component of the WBS with milestones,
deliverables, activities, scope, and sometimes dates, resources, costs, quality.
Plan outcomes, not actions
If the work breakdown structure designer attempts to capture any action-

oriented details in the WBS, s/he 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. For new product development projects, the most common
technique to ensure an outcome-oriented WBS is to use a product breakdown
structure. Feature-driven software projects may use a similar technique which is
to employ a feature breakdown structure. 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).
Example
The figure on the left shows a work breakdown structure construction technique
that demonstrates the 100% rule and the "progressive elaboration" technique. At
WBS Level 1 it shows 100 units of work as the total scope of a project to design
and build a custom bicycle. At WBS Level 2, the 100 units are divided into
seven elements. The number of units allocated to each element of work can be
based on effort or cost; it is not an estimate of task duration.
The three largest elements of WBS Level 2 are further subdivided at Level 3.
The two largest elements at Level 3 each represent only 17% of the total scope
of the project. These larger elements could be further subdivided using the
progressive elaboration technique described above.
WBS design can be supported by software (e.g. a spreadsheet) to allow

automatic rolling up of point values. Estimates of effort or cost can be
developed through discussions among project team members. This collaborative
technique builds greater insight into scope definitions, underlying assumptions,
and consensus regarding the level of granularity required to manage the
projects.
Misconceptions
 A WBS is not an exhaustive list of work. It is instead a comprehensive

classification of project scope.
 A WBS is neither a project plan, a schedule, nor a chronological listing. It

specifies what will be done, not how or when.
 A WBS is not an organizational hierarchy, although it may be used when

assigning responsibilities. See also: responsibility assignment (RACI)
matrix (also called a Staffing Matrix).

Work Breakdown Structure

Uploaded by

Copyright:

Available Formats

Work Breakdown Structure

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Work Breakdown Structure

Uploaded by

Copyright:

Available Formats

Work Breakdown

A work breakdown structure element may be a product, data, service, or any

WBS is a hierarchical and incremental decomposition of the project into phases,

A work breakdown structure permits summing of subordinate costs for tasks,

Defense Materiel Item categories from MIL-STD-881C are:

 Aircraft Systems WBS

 Electronic Systems WBS

 Ordnance Systems WBS

 Sea Systems WBS

 Space Systems WBS

 Surface Vehicle Systems WBS

 Unmanned Air Vehicle Systems WBS

 Unmanned Maritime Systems WBS

 Launch Vehicle Systems WBS

 Automated Information Systems WBS

The common elements identified in MIL-STD-881C, Appendix L are:

In 1987, the Project Management Institute (PMI) documented the expansion of

Mutually exclusive elements

Mutually exclusive: In addition to the 100% rule, it is important that there is no

Plan outcomes, not actions

If the work breakdown structure designer attempts to capture any action-

WBS design can be supported by software (e.g. a spreadsheet) to allow

 A WBS is not an exhaustive list of work. It is instead a comprehensive

 A WBS is neither a project plan, a schedule, nor a chronological listing. It

 A WBS is not an organizational hierarchy, although it may be used when

You might also like