Decomposition
DE: Zerlegung
Breaking down project scope into smaller, manageable components.
Detailed Explanation
Decomposition divides project scope and deliverables into smaller, manageable parts. It is the primary technique for creating the Work Breakdown Structure (WBS), the foundation of project planning.
The process starts at the highest level and progressively breaks work into work packages — the lowest WBS level where cost and duration can be estimated. The 100% rule requires the WBS to capture all project scope.
The 8/80 rule guides sizing: no work package should be less than 8 hours or more than 80 hours. Too little decomposition means unmanageable packages; too much creates overhead.
Key Points
- Primary technique for creating the WBS
- Breaks project-level work to work packages
- 100% rule: WBS must capture all scope
- 8/80 rule: work packages should be 8-80 hours
- Enables accurate cost, duration, resource estimation
- Foundation for all subsequent planning
Practical Example
Website redesign: Level 1 = Project; Level 2 = Design, Development, Content, Testing, Launch; Level 3 under Development = Frontend, Backend, Database, Integrations; Level 4 under Frontend = Homepage, Product Pages, Cart, Checkout. Each Level 4 item is a work package estimated at 20-60 hours.
Tips for Learning and Applying
Involve the team — they know the work best
Apply the 100% rule rigorously
Use the 8/80 rule for work package sizing
Decompose deliverables, not activities — the WBS is product-oriented
Want to Master These Concepts?
Our courses cover all these terms in depth with practical examples and exercises.