Session Outline
• What is a WBS and where is it useful?
• What is successive decomposition?
• How is the WBS used on a program?
• How can I tell if I have a good WBS?
• Numbering notation.
• Examples.
• Common errors.
Day 0, P2 Work Breakdown Structure Review & Prep!
CVISN Planning Workshop
3/14/2016 1:56 AM
The Johns Hopkins University Applied Physics Laboratory
Outline
P2 - 1
Where is WBS Useful?
• Rocket Science?
• Brain Surgery?
• CVISN?
Day 0, P2 Work Breakdown Structure Review & Prep!
CVISN Planning Workshop
3/14/2016 1:56 AM
The Johns Hopkins University Applied Physics Laboratory
P2 - 2
The Work Breakdown Structure Is...
• “Product-oriented hierarchy of goods and services.”
• Form: inverted tree; or indented list.
• Visualizing the entire project.
• Common framework for planning and control.
• Vehicle to divide work into tasks that are:
• Manageable
• Independent
• Measurable
• Integratable
• Graphically displays entire project.
• Clear definition of all effort.
• “Top Assembly Drawing” of the project.
• “Product Breakdown Structure” or “Project Breakdown Structure” more
apt name! Or perhaps “Work Buildup Structure”.
Day 0, P2 Work Breakdown Structure Review & Prep!
CVISN Planning Workshop
3/14/2016 1:56 AM
The Johns Hopkins University Applied Physics Laboratory
WBS Definition
P2 - 3
Create a WBS via Recursive
Product-Oriented Decomposition
(Call This Level 1)
Associated Support
Service Level 2
Principal Product
Principal Product
Associated Support
Product Level 2
more decomposition
Associated Support
Service Level 3
Sub-Product
Sub-Product
Associated Support
Product Level 3
more decomposition
Associated Support
Service Level 4
Sub-SubProduct(s)
Associated Support
Product Level 4
and so on, while it makes sense
Day 0, P2 Work Breakdown Structure Review & Prep!
CVISN Planning Workshop
3/14/2016 1:56 AM
The Johns Hopkins University Applied Physics Laboratory
WBS Construction
P2 - 4
2000-01-26
Example: Break Down 100% (1 of 2)
100%
Decomposition
Day 0, P2 Work Breakdown Structure Review & Prep!
CVISN Planning Workshop
3/14/2016 1:56 AM
The Johns Hopkins University Applied Physics Laboratory
Summation
2000-01-26
P2 - 5
Example: Break Down 100% (2 of 2)
100%
10%
20%
60%
10%
more decomposition
5%
20%
25%
10%
more decomposition
2%
20%
3%
and so on, while it makes sense
Summation
Day 0, P2 Work Breakdown Structure Review & Prep!
CVISN Planning Workshop
3/14/2016 1:56 AM
The Johns Hopkins University Applied Physics Laboratory
2000-01-26
P2 - 6
By decomposing, eventually.....
(Call This Level 1)
Associated Support
Services Level 2
Principal Product(s)
Associated Support
Products Level 2
More
More
Decomposition
More
Decomposition
Decomposition
More
More
Decomposition
More
Decomposition
Decomposition
More
More
Decomposition
More
Decomposition
Decomposition
More
More
Decomposition
More
Decomposition
More
Decomposition
More
Decomposition
More
Decomposition
Decomposition
More
More
Decomposition
More
Decomposition
More
Decomposition
More
Decomposition
More
Decomposition
Decomposition
More
More
Decomposition
More
Decomposition
More
Decomposition
More
Decomposition
More
Decomposition
Decomposition
.....you get to activities that
can be assigned and
scheduled.
Program
More
More
More
More
More
More
Decomposition
Decomposition
Decomposition
More
More
More
More
More
More
Decomposition
Decomposition
Decomposition
More
More
More
More
More
More
Decomposition
Decomposition
Decomposition
Decomposition
Decomposition
Decomposition
More
More
More
More
More
More
Decomposition
Decomposition
Decomposition
Decomposition
Decomposition
Decomposition
More
More
More
More
More
More
Decomposition
Decomposition
Decomposition
Decomposition
Decomposition
Decomposition
More
More
More
Decomposition
Decomposition
Decomposition
Decomposition
Decomposition
Decomposition
More
More
More
Decomposition
Decomposition
Decomposition
Decomposition
Decomposition
Decomposition
Project
Program Integration
Activity Plan
CVISN
Program
Project Integration Plan
Project Integration Plan
Safety
Credentialing
Product
Product Activity Plan
IRP
Day 0, P2 Work Breakdown Structure Review & Prep!
CVISN Planning Workshop
3/14/2016 1:56 AM
The Johns Hopkins University Applied Physics Laboratory
Product Activity Plan
Product Activity Plan
CVIEW
CI
WBS Construction
P2 - 7
Example Extended WBS for a Complex Program
• Note the different orientations
from top to bottom.
• WBS unfolds and evolves as
scope and design become known.
The Work to
be Done!
Day 0, P2 Work Breakdown Structure Review & Prep!
CVISN Planning Workshop
3/14/2016 1:56 AM
The Johns Hopkins University Applied Physics Laboratory
WBS Definition
P2 - 8
WBS for Brain Surgery (tree format)
Surgical Treatment
Project
1.0 Diagnosis
2.0 Plan for
Operation
3.0 Preoperative
Patient Care
4.0 Execution of
Operation
5.0 Postoperative
Patient Care
6.0 Long-Term
Patient Care
History
Communications Among
Team
Verify Patient Can Handle
Stress of Surgery
Verify Patient Identity &
Location of Surgery
Written Care Orders
Follow-up Clinical Visits
Clinical Exam
Patient & Team
Positioning
Stop Drugs that Would
Interfere with Surgery
Anesthesia
Briefing of Recovery Staff
by Surgeon
Physical Therapy
(for neurosurgery)
Imaging
Acquisition of Needed
Instruments & Equipment
Patient Under
the Knife
Vital Signs &
Fluid-Loss Monitoring
Blood &
Tissue Tests
Scheduling of Needed
Specialists
Vital Signs &
Fluid-Loss Monitoring
Neurophysiological
Monitoring
Likely Diagnosis
Practice Run-Throughs
Neurophysiological
Monitoring
(during neurosurgery)
Risk Assessment
Maintain Neat & Clean
Operative Field
Education of Patient
Wrap-up: Verify
Small Part Count
(sponge, needle, cottonoid, Michel clips)
Alternative Analysis
& Trade-Offs
Operative Notes &
Chart Updates
Treatment Plan
Sources:
1. Bailey & Loves’s Short Practice of Surgery, 22nd Edition, edited by Charles V. Mann, R.C.G.
Russell, and Norman S. Williams. Chapman & Hall Medical, 1995. ISBN 0-412-49490-6.
2. Brain Surgery – Complication Avoidance and Management, by Michael L. J. Apuzzo, M.D.
Churchill Livingstone, Inc., 1993. ISBN 0-443-08709-1. See Chapter 1, “Preoperative and Surgical
Planning for Avoiding Complications” by Robert G. Grossman.
Day 0, P2 Work Breakdown Structure Review & Prep!
CVISN Planning Workshop
3/14/2016 1:56 AM
The Johns Hopkins University Applied Physics Laboratory
P2 - 9
WBS for Brain Surgery (indented list)
Surgical Treatment Project
1.0 Diagnosis
History
General Medical Condition
Specific Complaint
Clerking?? (for elective surgery??)
Clinical Exam
Imaging
Ultrasonography
Plain Radiography (X-Ray)
Computed Tomography (CAT Scan)
Magnetic Resonance Imaging (MRI)
Blood and Tissue Tests
Likely Diagnosis
Risk Assessment
Education of Patient (e.g. anatomy)
Alternative Analysis & Trade-Offs
Treatment Plan
2.0 Planning of the Operation
Communications Among Team
Patient and Team Positioning (for neurosurgery)
Acquisition of Needed Instruments & Equipment
Scheduling of Needed Specialists
Practice Run-Throughs
3. 0 Preoperative Patient Care
Verify Patient can Handle Stress of Surgery
Stop Drugs that Would Interfere with Surgery
4.0 Execution of the Operation (Actual Surgery)
Verify Patient Identity and Location of Surgery
Anesthesia
Patient Under the Knife
Real-time Diagnostic Biopsies
Therapeutic Surgery
Vital Signs and Fluid-Loss Monitoring
Neurophysiological monitoring (during neurosurgery)
Maintain Neat and Clean Operative Field
Wrap-up: Verify Small Part Count (sponge,
needle, cottonoid, Michel clips)
Operative Notes and Chart Updates
5.0 Postoperative Care
Written Care Orders
Briefing of Recovery Staff by Surgeon
Vital Signs and Fluid-Loss Monitoring
Neurophysiological Monitoring
6.0 Long-Term Patient Care
Follow-up Clinical Visits
Physical Therapy
Day 0, P2 Work Breakdown Structure Review & Prep!
CVISN Planning Workshop
3/14/2016 1:56 AM
The Johns Hopkins University Applied Physics Laboratory
P2 - 10
WBS is The Basis For......
• Cost estimates and budgets.
• Milestones & schedules.
• Responsibility assignment.
• Allocation of resources.
• Schedule horizontal and vertical traceability.
• Risk analysis.
• Concurrence of participants.
• Integrating the total project effort.
• Summarizing costs, schedules, performance.
• Forcing the Project Manager to think through all elements
of the project.
Day 0, P2 Work Breakdown Structure Review & Prep!
CVISN Planning Workshop
3/14/2016 1:56 AM
The Johns Hopkins University Applied Physics Laboratory
WBS Definition
P2 - 11
Tests for a Good WBS:
 Product-oriented hierarchy of goods and services.
 Top level may be dictated by contract.
 Basis for cost estimating, project organization, assigning responsibility,
task scheduling, and status reporting.
 Basis for understanding and communication.
 Each element should be “manageable”.
 Based on System Engineering: interfaces are minimized; units are
stand-alone testable.
 Eliminating one product element will delete the associated costs.
 Segregate recurring from non-recurring costs.
 Identifies and defines all effort to be expended: correlation of lower
levels to specification tree, contract line items, data items, and work
statement tasks.
 Useful! Reflects the way the work is managed and performed.
 Sufficiently low level to establish adequate visibility and confidence for
cost estimating, project planning, and project control.
 Technical/cost/schedule can be integrated at every level for each
element.
Day 0, P2 Work Breakdown Structure Review & Prep!
CVISN Planning Workshop
3/14/2016 1:56 AM
The Johns Hopkins University Applied Physics Laboratory
WBS Definition
P2 - 12
WBS Levels & Numbering Notation
Satellite Mission Project
1. Project Management
2. Science Instruments
Level 1
3. Spacecraft Bus
4. Ground Support Equipment
Level 2
2.1 Magnetometer
3.1 Propulsion Subsystem
2.2 Spectrograph
3.2 Attitude Control Subsystem
3.3 Command & Data Handling Subsystem
Satellite Mission Project (Level 1)
1. Project Management (Level 2)
2. Science Instruments
2.1 Magnetometer
2.2 Spectrograph
3. Spacecraft Bus
3.1 Propulsion Subsystem (Level 3)
3.2 Attitude Control Subsystem
3.3 Command & Data Handling Subsystem
3.3.1 C&DH Hardware (Level 4)
3.3.1.1 Processor Card (Level 5)
3.3.1.2 Memory Card
3.3.2 C&DH Software
3.3.3 Subsystem Integration
4. Ground Support Equipment
3.3.1 C&DH Hardware
3.3.1.1 Processor Card
Level 3
Level 4
Level 5
3.3.1.2 Memory Card
3.3.2 C&DH Software
3.3.3 Subsystem Integration
Day 0, P2 Work Breakdown Structure Review & Prep!
CVISN Planning Workshop
3/14/2016 1:56 AM
The Johns Hopkins University Applied Physics Laboratory
WBS Definition
P2 - 13
Scenario Exercise
Imagine you are working at the
Atlantic Pacific Sea Vision
Fountain Pen Manufacturing Company
Motto: “Yesterday’s Technology Solving
Today’s Problems Tomorrow”
Let’s develop a WBS for our proposed
mechanical pencil project.
Day 0, P2 Work Breakdown Structure Review & Prep!
CVISN Planning Workshop
3/14/2016 1:56 AM
The Johns Hopkins University Applied Physics Laboratory
Exercise
P2 - 14
Where Does the Work Get Done?!!
Satellite Mission Project
Product-Oriented
Nouns
1. Project Management
2. Science Instruments
3. Spacecraft Bus
3.1 Propulsion Subsystem
3.2 Attitude Control Subsystem
3.3 Command & Data Handling Subsystem
3.3.1 C&DH Hardware
3.3.1.1 Processor Card
3.3.1.1.1 Engineering Design
3.3.1.1.2 Layout & Package Design
3.3.1.1.3 Fabrication
3.3.1.1.4 Assembly & Test
3.3.2 C&DH Software
3.3.2.1 Command Parsing Module
3.3.2.1.1 Architectural Design
3.3.2.1.2 Detailed Design
3.3.2.1.3 Coding
3.3.2.1.4 Unit Test
3.3.3 Subsystem Integration
3.3.3.1 Integration Plan
3.3.3.1 Integrate Instruments with Bus
4. Ground Support Equipment
Day 0, P2 Work Breakdown Structure Review & Prep!
CVISN Planning Workshop
3/14/2016 1:56 AM
The Johns Hopkins University Applied Physics Laboratory
Process-Oriented
Here is real work!
Verbs
WBS Definition
P2 - 16
Typical WBS for a State CVISN Program
State
CVISN Program
Level 1
Level 2
Level 3
1. Program
Management
2. System
Engineering &
Integration
3. Safety
Project
4. Credentials
Project
5. E-Screening
Project
6. Evaluation
1.1 Planning &
Coordination
2.1 System
Requirements
Definition
3.1 Proj Mgt
4.1 Proj Mgt
5.1 Proj Mgt
6.1 Self-Evaluation
1.2 Carrier
Coordination
2.2 System
Design
3.2 Sys Engr &
Integration
4.2 Sys Engr &
5.2 Sys Engr &
Integration
6.2 National Evaluation
(Funded Separately)
1.3 Showcases
& Outreach
2.3 Architecture
Conformance
3.3 Subcontract &
Procurement Mgt
4.3 Subcontract &
Procurement Mgt
5.3 Subcontract &
Procurement Mgt
1.4 Regional
Coordination
2.4 System
Integration
and Test
3.4 CV Information
Exchange
Window (CVIEW)
4.4 International
Registration
Plan (IRP)
5.4 Roadside
Operations
1.5 O & M Planning
2.5 Interoperability
Testing
3.5 ASPEN
4.5 International
Fuel Tax
Agreement (IFTA)
5.5 Screening
1.6 Training
3.6 SAFETYNET
4.6 Credentialing
Interface
5.6 Site Mods
1.7 Policy
3.7 Builds 1...n
4.7 Motor Carrier
Home Page &
Web Credentialing
5.7 Carrier
E-Screening
Enrollment
4.8 Carrier Cred
Systems
(CAT or module)
5.8 Builds 1...n
1.8 Subcontract &
Procurement Mgt
4.9 Intra-State
Registration
4.10 Builds 1...n
Day 0, P2 Work Breakdown Structure Review & Prep!
CVISN Planning Workshop
3/14/2016 1:56 AM
The Johns Hopkins University Applied Physics Laboratory
WBS Sample
P2 - 17
2001-06-14
Elements Not to Include in WBS
• Do not use the structure of the contractor’s organization as the basis
of a WBS.
• At the top levels do not begin by decomposing into the functions or
cost categories associated with developing those products.
What not to do!
Program
Design
Build
Test
Adapted from Department of Defense Handbook –
Work Breakdown Structure, MIL-HDBK-881.
Available at:
http://www.acq.osd.mil/pm/newpolicy/wbs/wbs.html.
Includes examples from the defense industry.
Hardware
Software
• Do not use generic names -- use actual system names and
nomenclature.
• No disembodied software -- software developed to reside on specific
equipment must be identified as a subset of that equipment.
Day 0, P2 Work Breakdown Structure Review & Prep!
CVISN Planning Workshop
3/14/2016 1:56 AM
The Johns Hopkins University Applied Physics Laboratory
WBS Definition
P2 - 18
Common Errors When Creating WBS
• Does not include all of the work.
• Example: The project calls for a prototype and a final version, but the WBS shows only one of
these. Or it shows the prototype in detail, and then simply lists the other without showing the
work needed to produce it.
• The level of detail is not sufficient to manage the
program.
• Example: The big pieces may be there, but they are not broken down sufficiently to enable the
work to be assigned, tracked, and managed. (The test would be: Can you use this WBS to
make a good, detailed CPM network?)
• Important but not readily apparent steps are left out.
• Example: The omission of integration and testing.
• The work is there, but it’s not arranged logically.
• Example: Lower-level product integration and testing is there, but its off on its own and you
cannot tell what it is to be applied to or when.
Day 0, P2 Work Breakdown Structure Review & Prep!
CVISN Planning Workshop
3/14/2016 1:56 AM
The Johns Hopkins University Applied Physics Laboratory
WBS Definition
P2 - 19