Work Breakdown Structure (WBS)
Hierarchical breakdown of a project into sub-tasks down to individual work packages, forming the basis for schedule, cost, and resource planning.
A work breakdown structure decomposes an overall project step by step into smaller, manageable parts: from project phases through sub-tasks down to work packages, the smallest unit that can still be planned, scheduled, and assigned to a responsible person as a whole.
This decomposition provides a complete overview of a project's total scope. Nothing should appear twice and nothing should be missing; the principle is often summarised as MECE: mutually exclusive, collectively exhaustive.
Based on the work packages, schedules, costs, and required resources can then be estimated realistically, because each package is small enough to be calculable with confidence. The work breakdown structure thus forms the foundation for schedules, network plans, and ultimately for identifying the critical path.
Practical Example
For the rollout of a new ERP system, a company structures its work breakdown structure into the sub-tasks requirements analysis, system selection, data migration, training, and go-live. Data migration is further split into work packages such as data cleansing, test import, and final cutover.
How Leanshift Helps
A clean work breakdown structure forces you to break a large undertaking into achievable steps before starting, the same mindset that also helps with improving processes step by step.
Frequently Asked Questions
How deep should a work breakdown structure go?
Deep enough that every work package is clearly schedulable, costable, and assignable to one person, often three to four levels.
Is a work breakdown structure organised by function or by phase?
Both are common, as are mixed forms; what matters is that the chosen structure stays clear for the specific project.