A Work Breakdown Structure is a hierarchical decomposition of the total scope of a program into progressively smaller, manageable elements. It organizes and defines 100% of the program scope. Each descending level adds detail. The lowest level elements (work packages) are where work is planned, budgeted, executed, and measured.

What is the 100% rule?

The 100% rule states that the WBS must capture 100% of the program scope — no more, no less. Every child element must account for 100% of its parent. If you add the budgets of all children, they must equal the parent. If work exists that is not in the WBS, it is out of scope or the WBS is incomplete.

What is the difference between product and functional WBS?

A product-oriented WBS is organized by deliverable (aircraft, wing, fuselage, systems). A functional WBS is organized by type of work (engineering, manufacturing, test, quality). A hybrid combines both — typically product-oriented at the top levels and functional at lower levels. Most aerospace programs use product-oriented per MIL-STD-881.

Work Breakdown Structure: The Foundation of Program Control

New to this topic?

We recommend reading these guides first to get the most out of this one:

EVMS Fundamentals

100%

Scope Rule

3–6

Typical Levels

WBS × OBS

= Control Accounts

881

MIL-STD Reference

Why WBS Comes First

You cannot plan, budget, schedule, or measure a program without first defining what the program contains. The WBS is that definition. Every other EVMS artifact depends on it: the schedule is organized by WBS. The budget is distributed by WBS. Earned value is measured by WBS. Cost is collected by WBS. If the WBS is wrong, everything built on it is wrong.

WBS Decomposition Rules

Rule 1: 100% Rule

Each level must capture 100% of the scope at that level. Nothing missing, nothing extra. The sum of all Level 3 elements must equal 100% of the Level 2 element they belong to.

Rule 2: Mutually Exclusive

No overlap between elements at the same level. If “Wing Assembly” includes sealant application, then “Fuselage Assembly” must not also include wing sealant. Double-counting scope means double-counting budget.

Rule 3: Outcome-Oriented

WBS elements should describe deliverables or outcomes, not activities. Not “Drilling” but “Wing Rib Assembly” (which includes drilling as one of many activities). Activities belong in the schedule; deliverables belong in the WBS.

Rule 4: Appropriate Depth

Decompose to the level where you can meaningfully plan, budget, and measure. Too shallow = elements too large to manage. Too deep = excessive administrative overhead. Typical aerospace programs: 3–6 levels, with the lowest level (work packages) representing 1–3 months of effort.

Aerospace WBS Example

📊 Fighter Aircraft WBS (Top 3 Levels) MIL-STD-881 Based

Level 1	Level 2	Level 3 (Examples)
1.0 Aircraft System	1.1 Air Vehicle	1.1.1 Airframe, 1.1.2 Propulsion, 1.1.3 Vehicle Subsystems
	1.2 System Engineering	1.2.1 Requirements Analysis, 1.2.2 System Design, 1.2.3 Integration & Test
	1.3 Training	1.3.1 Pilot Training, 1.3.2 Maintenance Training, 1.3.3 Training Devices
	1.4 Support Equipment	1.4.1 GSE, 1.4.2 Test Equipment
	1.5 Data	1.5.1 Technical Publications, 1.5.2 Engineering Data
	1.6 Program Management	1.6.1 PM Office, 1.6.2 Contract Admin, 1.6.3 Reviews
	1.7 System Test & Evaluation	1.7.1 DT&E, 1.7.2 OT&E

Level 1 is the total program. Level 2 is defined by MIL-STD-881 for each commodity type. Level 3 and below are contractor-defined based on program architecture and organizational structure.

WBS Dictionary

Every WBS element needs a dictionary entry that defines exactly what is included and excluded. Without the dictionary, two people looking at “1.1.1 Airframe” may have different assumptions about what it contains.

Field	Content
WBS Element	1.1.1 Airframe
Description	Design, fabrication, and assembly of the aircraft structural airframe including fuselage, wing, and empennage structures
Includes	Structural design, detail part fabrication, subassembly, final structural assembly, structural test articles
Excludes	Avionics installation (1.1.3), propulsion installation (1.1.2), systems integration (1.2.3)
Responsible Org	Structures Engineering + Manufacturing

WBS × OBS = Control Accounts

The Organizational Breakdown Structure (OBS) maps the performing organizations. The intersection of WBS (what work) and OBS (who does it) creates the control account — the point where scope, schedule, budget, and responsibility converge.

WBS
(What)

OBS
(Who)

→

Control
Account

Each control account has one CAM (Control Account Manager) who is accountable for the scope, schedule, and budget within that intersection. The CAM track covers this role in detail.

⚠️ WBS Mistakes That Cascade

Missing scope: If work is not in the WBS, it has no budget. When it is eventually discovered, it is funded from management reserve (if available) or creates an overrun. Wrong level: Elements that are too large cannot be meaningfully measured; elements that are too small create administrative burden that exceeds the value of the control. Activity-oriented: A WBS organized by activity (“Design,” “Build,” “Test”) makes it impossible to track the cost of a deliverable across its lifecycle.

🎯 The Bottom Line

The WBS is the skeleton of program management. It defines 100% of the scope, organizes it hierarchically, and — when crossed with the OBS — creates the control accounts where EVMS actually operates. Get the WBS right and everything downstream (budgeting, scheduling, earned value measurement, variance analysis) has a solid foundation. Get it wrong and no amount of sophisticated analysis can compensate. Next: Earned Value Metrics — the measurements that turn WBS structure into performance insight.

Keep Learning

Work Package Planning

🏭

Free Process Modeler