PrepSolution
PMPHigh-YieldProcess 41%
the WBS is NOT a schedule, it is a decomposition of scope

WBS and Scope Management

100%

The Rule

WBS captures 100% of scope, no more, no less

4

Hierarchy Levels

Epic → Feature → Story → Task in agile

6

INVEST Criteria

Independent, Negotiable, Valuable, Estimable, Small, Testable

every box sums to its parent · 100% rule

Wedding Project · Sample WBS

1.0 Wedding1.1 Venue1.2 Ceremony1.3 Reception1.4 AttireContract signwp 1.1.1Rehearsalwp 1.2.1Sub-packages ↓wp 1.3.xDress + suitswp 1.4.1Cateringwp 1.3.1DJ + musicwp 1.3.2Cake + decorwp 1.3.3activities come LATER, during schedule planning · the WBS only says WHAT

how to read this

  • › The top box is the whole project. Everything below it must add up to 100% of what the project delivers — no more, no less.
  • Level 2boxes are major deliverables. Pick verbs like "secured," "booked," "signed" — they're outcomes, not tasks.
  • Level 3 boxes are work packages — small enough to estimate cost and duration, large enough to assign one owner.
  • › Reception breaks down further into Catering, DJ, Cakebecause it's complex. Other deliverables stay at one level. Decompose only where it helps.
  • › The WBS answers WHAT. The schedule answers WHEN. Never mix them up — activities and dates live in the schedule, not here.

INVEST · Story Quality Checklist

I

Independent

N

Negotiable

V

Valuable

E

Estimable

S

Small

T

Testable

Exam Traps

The WBS does not show sequence or dependencies

That is the network diagram. The WBS shows what is included, not when or in what order. Answers that confuse WBS with schedule are wrong.

Work packages are the lowest WBS level, not activities

Work packages are decomposed into activities during schedule planning, not during WBS creation. The exam tests this boundary.

The product backlog is living, the WBS is baselined

A WBS is approved and only changes through integrated change control. A product backlog is continuously refined by the PO. Treat them differently.

The 100% rule cuts both ways

The WBS must capture all required work AND exclude everything that is not required. Extra work is gold plating. Missing work is scope creep waiting to happen.

WBS is NOT a schedule

No dates, no sequence, no dependencies. Just what is in scope broken into work packages.

Scope baseline = 3 documents

Scope statement + WBS + WBS dictionary. All three together, approved, form the baseline.

1
The Whole Wedding

The top box of the WBS is "our wedding." That is 100% of scope. Every piece of the wedding must fit inside this box.

2
Major Deliverables

Break it into venue, ceremony, reception, photography, attire. Each is a deliverable, not a task. You do not "do" a venue — you deliver it.

3
Work Packages

Break reception into catering, DJ, decor, cake. These are work packages — small enough to estimate cost and duration, large enough to assign.

4
INVEST in Agile

If you were planning this as an agile project, the same wedding becomes epics (venue, reception) broken into stories that meet INVEST criteria. Same 100% coverage, different vocabulary.

WBS describes scope. Schedule describes order. Never confuse the two.
reading is not enough, you gotta practice

Ready to test your PMP knowledge?

1,800 practice questions written by certified professionals.

Start Practicing PMP
Reviewed by Chris K., PrepSolution Content Editor, Project Management
Sources verified against PMI 2026 standards
Updated May 2026