Project Scope and the Work Breakdown Structure (WBS)

What you'll learn

Write a scope statement with deliverables, acceptance criteria and exclusions.
Build a work breakdown structure (WBS) that covers 100% of the work.
Decide how far to decompose, using the 8/80 guideline for work packages.
Fill in a WBS dictionary entry so nobody has to guess what a task includes.
Recognize scope creep and gold plating, and stop both politely.

Project scope is the complete list of what the project will deliver, and just as important, what it won't. The work breakdown structure (WBS) takes that scope and breaks it into smaller and smaller pieces until each piece can be estimated, assigned and tracked. Together they are the foundation of the schedule, the budget and the risk list: anything missing from the WBS is missing from all three. In this lesson you'll build both for a construction job in Dayton, Ohio.

100%rule: the WBS must include all the work in scope, and nothing outside it

8–80 hcommon guideline for the size of a work package (the lowest WBS level)

3 levelsare enough for most small and mid-size projects

Write the scope statement
Break down the deliverables
Check the 100% rule
Size the work packages
Protect the scope

Project scope vs. product scope

There are two kinds of scope, and you need both:

Product scope describes the result: its features and specs. "A 1,200-square-foot garden center building with a heated sales floor and a covered loading area."
Project scope describes all the work needed to deliver it, including the work nobody sees: permits, inspections, project meetings, punch lists and closeout documents.

Beginners tend to list only the product. Then the schedule has no time for permits and the budget has no line for inspections. Project scope catches that.

Step 1: write the scope statement

The example: Miller Family Hardware, a third-generation store in Dayton, Ohio, is adding a garden center building next to its main store. The general contractor's PM writes this scope statement before building the schedule:

Element	Miller Family Hardware garden center
Project objective	Open a 1,200 sq ft garden center by April 1 for the spring season, for $290,000.
Main deliverables	Permitted design, foundation, framed and roofed building, electrical, plumbing and HVAC, finished interior, certificate of occupancy.
Acceptance criteria	Passes all city inspections; certificate of occupancy issued; punch list closed; owner walkthrough signed.
Exclusions (out of scope)	Shelving and fixtures (owner supplies), parking lot repaving, signage, point-of-sale equipment.
Assumptions	Soil conditions match the existing store's geotechnical report; utilities can tie into the main building.
Constraints	Store stays open during construction; no work before 7 a.m.; fixed opening date of April 1.

The exclusions row is the one that saves the most arguments. If the owner later asks "where's the sign?", the answer is already on paper, signed by both sides.

1. Why list exclusions in the scope statement?

To prevent misunderstandings about work the client might assume is included
To make the project look smaller and cheaper
Because exclusions are required by law in every state

Exclusions make expectations explicit. When a stakeholder later asks for something on the list, it becomes a documented change request instead of an argument about what was "obviously" included.

Step 2: break the deliverables into a WBS

A WBS is a hierarchy of deliverables. The top box is the whole project. Level 1 holds the major deliverables or phases. Each level below breaks its parent into smaller pieces until you reach work packages: chunks of work small enough to estimate, assign to one owner and track. Each element gets a code (1.1, 1.4.2…) that you'll reuse in the schedule and the budget.

A deliverable-oriented WBS: each box is a piece of the result (nouns), not an action. The activities to build each piece come later, in the schedule.

Deliverables, not activities

Notice that the boxes are nouns: "foundation," "electrical," "interior finishes." A WBS answers what will be produced. The verbs ("pour footings," "pull wire," "hang drywall") belong to the activity list you'll build in the scheduling lesson. Keeping the WBS deliverable-oriented makes it far easier to spot gaps, because you can ask, "If we deliver all these pieces, do we have the finished building?"

Step 3: check the 100% rule

The 100% rule says the WBS must include all the work defined by the scope, and the children of each element must add up to exactly 100% of their parent. Nothing missing, nothing extra. Costs make it easy to check:

WBS code	Element	Cost	Share
1.1	Design and permits	$28,000	9.7%
1.2	Site and foundation	$46,000	15.9%
1.3	Framing and roof	$72,000	24.8%
1.4	MEP systems (26,000 + 14,000 + 24,000)	$64,000	22.1%
1.5	Interior finishes	$58,000	20.0%
1.6	Project management and closeout	$22,000	7.6%
	Total (level 0)	$290,000	100%

Share of the $290,000 budget by WBS branch

1.3 Framing24.8%

1.4 MEP22.1%

1.5 Interiors20.0%

1.2 Foundation15.9%

1.1 Design9.7%

1.6 PM7.6%

Branch 1.6 is the one beginners forget: the project manager's time, site meetings, the punch list and closeout paperwork are real work and cost real money. That works out to about $242 per square foot all-in ($290,000 ÷ 1,200), a number the contractor can compare against past jobs.

2. A WBS element "Marketing launch" has a budget of $20,000. Its children are: website update $6,500, email campaign $3,000 and paid ads $8,000. What does the 100% rule tell you?

Everything is fine; children don't need to add up
$2,500 of work is missing from the children, or the parent budget is wrong
The parent should be reduced to the largest child, $8,000

6,500 + 3,000 + 8,000 = $17,500, which is $2,500 short of the parent's $20,000. Either a deliverable is missing (event, press release, creative production…) or the parent's estimate needs fixing.

Step 4: decide how deep to go

Stop breaking work down when each work package can be estimated with confidence, assigned to one person or crew, and completed in a reasonable period. A common guideline is the 8/80 rule: a work package should take somewhere between 8 and 80 hours of effort. Smaller than that and you're micromanaging; larger and it's too big to track (you'll hear "it's 90% done" for three weeks).

Another practical test: can progress be checked within one reporting period? If you report weekly, a work package that takes six weeks gives you no real signal until it's late.

3. Using the 8/80 guideline, which work package should be broken down further?

"Install bathroom fixtures," estimated at 12 hours
"Paint sales floor," estimated at 40 hours
"Electrical systems," estimated at 220 hours

220 hours is far above 80, so it should be split, for example into service and panel, rough-in wiring, lighting fixtures, and testing. The other two fall within 8–80 hours.

The WBS dictionary

A box that says "Plumbing" means different things to different people. The WBS dictionary adds a short entry for each work package so nobody has to guess:

Field	1.4.2 Plumbing
Description	Water supply, drains and one utility sink; tie-in to the main building's water line.
Owner	Plumbing subcontractor (foreman: D. Kowalski)
Acceptance criteria	Passes the city's rough-in and final plumbing inspections; no leaks in a 24-hour pressure test.
Estimated effort and cost	70 hours, $14,000
Depends on	1.2 Foundation (under-slab lines), 1.3 Framing

Step 5: protect the scope

Once the scope is agreed, two forces will try to grow it. Both feel harmless in the moment:

Scope creepThe client keeps adding "small" things

Example: "While you're at it, can you add a second roll-up door?"
Why it hurts: Each request seems tiny; together they blow the budget and the date.
Fix: Log every request as a change request with its cost and time impact.

Comes from outside

Gold platingThe team adds extras nobody asked for

Example: The electrician installs premium fixtures "because it looks better."
Why it hurts: Uses budget and time on things the client didn't request or approve.
Fix: Deliver what's in scope; suggest upgrades as options, never as surprises.

Comes from inside

Writing the WBS as a to-do list of activities.

Use deliverables (nouns) for the WBS; save verbs for the schedule.

Forgetting project management, testing and closeout work.

Give them their own branch so they get time and budget.

Breaking everything down to 2-hour tasks.

Stop at work packages of roughly 8–80 hours.

Accepting "small" additions with a handshake.

Every addition, however small, goes through change control.

4. Without asking anyone, a developer adds an animated welcome screen that wasn't in the requirements. What is this called?

Gold plating
Scope creep
Progressive elaboration

Gold plating is extra work added by the team without a request or approval. Scope creep comes from stakeholders adding requests without going through change control.

Practice exercise

A nonprofit in Columbus, Ohio is organizing a charity 5K run with a $13,000 budget. The draft WBS has five level-1 elements: venue and permits ($3,200), marketing ($2,400), race-day logistics ($5,600), registration and sponsors ($1,300) and project management ($500). Race-day logistics breaks down into timing chips ($1,800), water stations ($900) and portable restrooms ($1,100).

(a) Does the level-1 budget satisfy the 100% rule? (b) Does race-day logistics? (c) What would you suggest?

See solution

(a) 3,200 + 2,400 + 5,600 + 1,300 + 500 = $13,000. Level 1 adds up to the total.

(b) 1,800 + 900 + 1,100 = $3,800, which is $1,800 short of the $5,600 parent. Something is missing.

(c) Ask what the remaining $1,800 covers. For a city race, a likely gap is police and traffic control (road closures usually require it). Add it as 1.3.4 Security and traffic control, $1,800, so the branch totals $5,600. Then write a WBS dictionary entry for it with the city's requirements as acceptance criteria.

Summary

Product scope describes the result; project scope adds all the work needed to deliver it.
A good scope statement lists deliverables, acceptance criteria, exclusions, assumptions and constraints.
The WBS breaks deliverables into work packages; codes like 1.4.2 link it to the schedule and budget.
The 100% rule: children add up to exactly their parent. Use costs or hours to check it.
Size work packages at roughly 8–80 hours and describe them in a WBS dictionary.
Scope creep comes from outside, gold plating from inside; change control stops both.

Next lesson: Stakeholder Management and the Communication Plan. You'll map who can make or break your project and plan exactly what each person needs to hear, and when.