What is a work breakdown structure (WBS)?

What a WBS looks like

At the top is the project itself. Beneath it are the major deliverables or phases, beneath those the components of each, and so on down. The pieces at the very bottom — the ones that are not broken down any further — are usually called work packages, and they are what actually gets scheduled and done.

Each item gets an outline number that records where it sits: 2 is the second top-level item, 2.3 is the third item inside it, 2.3.1 the first item inside that. The numbers let anyone refer to a piece of work unambiguously, and they are how many scheduling tools — Waterfall PM included — let you write dependencies as text.

• 1 Site preparation — 1.1 Survey, 1.2 Demolition, 1.3 Excavation
• 2 Foundation — 2.1 Formwork, 2.2 Pour, 2.3 Cure and strip
• 3 Fit-out — 3.1 Electrical rough-in, 3.2 Drywall, 3.3 Paint

The 100% rule

The single most useful rule for a WBS: the children of any item must add up to 100% of that item — no more, no less. Nothing in the project should be missing from the WBS, and nothing in the WBS should be outside the project.

In practice this is a checklist. For every parent, ask whether finishing all of its children would finish it. If the answer is “not quite”, something is missing — often the unglamorous work: approvals, testing, hand-over, documentation.

Deliverables at the top, work at the bottom

Upper levels read best as nouns — the things the project produces (“Foundation”, “User documentation”). The work packages at the bottom read best as verbs — the work that produces them (“Pour the slab”, “Write the install guide”). Organising the top by deliverable rather than by department keeps the structure stable when people change.

How far to break it down

Stop when a piece is small enough that one person or team can estimate it with confidence and you would notice within a reporting period if it slipped. A common rule of thumb puts work packages between about one day and two weeks of effort; much smaller and the plan becomes a to-do list, much larger and nobody can tell whether it is on track.

It is fine for branches to have different depths. A well-understood phase might stop at the second level while a risky one goes down five.

From WBS to schedule

A WBS says what the work is; a schedule says when. To get from one to the other, give each work package a duration and connect it to the work it depends on. A scheduling engine then works out every start and finish date and the critical path — the chain of work that decides when the project ends.

In Waterfall PM those are the same table. Phases roll their dates up from their children, leaf tasks carry a duration and their predecessors, and the Gantt chart beside the WBS is recalculated after every change. Insert adds a row, Tab and Shift+Tab indent and outdent, and dependencies are typed as outline numbers — 1.3FS or 2.1SS+2d.