WBS (Work Breakdown Structure)
A WBS (Work Breakdown Structure) is a hierarchical, deliverable-oriented decomposition of a project's total scope. Everything the project must produce lives somewhere in this tree.
What a WBS decomposes
A WBS decomposes scope — not schedule, not people. The project sits at the top; phases and deliverables branch below it, down to work packages. The unit of decomposition is an outcome, not an activity: "payment module," not "do development."
Why it matters
Because it turns scope completeness into a structural property. The 100% Rule — a parent's scope must equal the sum of its children — is the backbone. On a systems-integration project, if "data migration rehearsal" is missing from the WBS, it is missing from the estimate and the schedule too, and that absence usually surfaces right before go-live. The WBS is the shared map that contracts, estimates, and progress reports all point at.
Common misconceptions
A WBS is not a to-do list. A to-do list encodes sequence; a WBS encodes containment. Sequence and dates are layered on top with dependencies and a schedule. And the WBS code (1.2.3) is display numbering, not identity — rearrange the tree and the numbers change.
wbsgantt edits the WBS tree with drag and drop, renumbers codes automatically, and validates that sibling weights sum to 100 out of the box.