A work breakdown structure (WBS) breaks the whole scope into smaller and smaller pieces, top down. The top is the project; the next level is its major deliverables; the lowest level is work packages, pieces small enough to estimate, assign and track.
Rules that keep a WBS useful:
- The 100% rule: the children of an element add up to all of it, no more and no less. Nothing in scope is missing, and nothing outside scope sneaks in. Project management work counts too.
- Deliverables, not activities: elements are nouns ("Children's area walls"), not verbs ("Paint the walls"). The activities come later, in the schedule.
- No overlap: each piece of work sits in exactly one place, or it gets estimated and paid for twice.
Each element gets a WBS code that shows where it sits: 1.2 is the second deliverable, 1.2.3 the third work package under it.
A WBS with codes: deliverables, then work packages.