What is the 100% rule in WBS?

The 100% rule states that the WBS must include 100% of the work defined by the project scope. Each level of the WBS must represent 100% of the work in its parent element. This ensures nothing is missed and prevents scope gaps. If you add up all the work packages, they should account for the complete project scope - no more, no less.

How detailed should a WBS be?

Decompose until work packages are manageable - typically 8-80 hours of effort per work package (the "8/80 rule"). Work packages should be small enough to estimate, assign, and track, but not so small that the overhead of managing them exceeds their value. For Agile projects, the WBS may map to epics and stories rather than traditional work packages.

Is WBS used in Agile?

Traditional WBS is less common in Agile, but the concept of hierarchical decomposition is present: Themes/Initiatives → Epics → Stories → Tasks. This serves the same purpose - breaking down large scope into manageable, estimable, and assignable pieces. Some Agile teams create a lightweight WBS for initial scope mapping before decomposing into stories during backlog refinement.

Book Free Assessment Calculator

Work Breakdown Structure (WBS)

Work Breakdown Structure

Also known as:WBSscope decompositiondeliverable breakdown

A hierarchical decomposition of the total scope of work into smaller, manageable components, breaking down project deliverables into progressively more detailed levels.

In-Depth Explanation

A Work Breakdown Structure (WBS) organises a project's total scope into a hierarchical structure of deliverables and work packages. It is a fundamental planning tool that ensures nothing is overlooked and that the scope is fully understood.

WBS structure:

Level 1: The project itself (top level)
Level 2: Major deliverables or phases
Level 3: Sub-deliverables or major tasks
Level 4: Work packages (lowest level of decomposition)

WBS types:

Deliverable-based: Organised around what is produced (recommended by PMI)
Phase-based: Organised around project phases
Functional-based: Organised around business functions or teams

WBS creation rules:

100% rule: The WBS must capture 100% of the project scope
Mutually exclusive: Work packages should not overlap
Outcome-oriented: Focus on deliverables, not activities
Progressive elaboration: Detail increases at lower levels
Work packages: The lowest level should be estimable, assignable, and manageable

Benefits of WBS:

Ensures no scope is missed (the 100% rule)
Provides a basis for cost and time estimation
Enables clear assignment of responsibility
Supports progress tracking at multiple levels
Facilitates communication about project scope
Serves as a foundation for the project schedule

WBS and other project management tools:

The WBS feeds into the project schedule (adding durations and dependencies)
The WBS feeds into the cost estimate (estimating each work package)
The WBS feeds into the RACI matrix (assigning responsibility to work packages)
The WBS supports risk identification (analysing each work package for risks)

WBS creation approach:

Start with major deliverables
Decompose each deliverable into its components
Continue decomposing until work packages are manageable (typically 8-80 hours of work)
Validate with the team and stakeholders
Use the WBS dictionary to define each element clearly

Business Context

A WBS ensures complete scope coverage, provides the foundation for accurate estimation and scheduling, and enables clear accountability for every aspect of project delivery.

How Clever Ops Uses This

Clever Ops uses work breakdown structures for complex client projects, ensuring complete scope coverage and clear deliverable definition. We help Australian businesses decompose large initiatives into manageable work packages that can be accurately estimated and tracked.

Example Use Case

"A project team decomposes an ERP implementation into major deliverables (requirements, configuration, data migration, integration, testing, training), then breaks each into work packages that can be individually estimated and assigned."