Demo environment — data may be reset without notice. Not for production use.
VanillaPM
Sign in Get started free Dashboard
Pr2 Process · 41%

Develop and manage project scope

In the app: Project → WBS (Overview · Tree · Scope validation) · Planning → Requirements · Traceability

PMP ECO · Process (41%) · Task Pr2. Define exactly what the project will and won't deliver, decompose it into work you can manage, prove each piece was asked for, and get each one formally accepted.

Agree what "done" means — scope in the short version

What it is

Scope work runs in five steps:

  1. Collect requirements. What the stakeholders need, each with a source and a way to verify it.
  2. Define scope. The scope statement: the description of the project, its major deliverables, and what is explicitly excluded.
  3. Create the WBS. The work breakdown structure decomposes the total scope into smaller pieces. The lowest level is the work package: the unit you estimate, schedule, cost and accept. Every level adds up to exactly its parent, no more and no less (the 100% rule).
  4. Validate scope. The customer formally accepts each completed deliverable.
  5. Control scope. Every change to scope goes through change control.

The scope baseline is the approved scope statement, WBS and WBS dictionary, the document that describes each WBS element, including its acceptance criteria. It changes only through formal change control, and progress is measured against it.

Two tools hold this together. The requirements traceability matrix (RTM) links each requirement from its origin to the deliverables that satisfy it, so every requirement is delivered and every deliverable has a reason to exist. And Validate Scope closes the loop: a deliverable is accepted against the criteria agreed in advance.

Why it matters

  • Everything else hangs off the WBS. The schedule, budget, resources and risks are all planned against its work packages. A missing package is missing time and money.
  • The boundary is what makes change visible. With a scope statement and a baseline, "can you just add…" becomes a change request instead of silent scope creep: growth in scope without adjusting time, cost and resources.
  • Traceability works both ways. A requirement with no deliverable won't get built. A deliverable with no requirement is either a requirement nobody wrote down or work nobody asked for.
  • Acceptance needs criteria agreed up front. Without them, "done" becomes an argument at handover.

Where you do it in VanillaPM

  • WBS → Overview: the structure note (numbering and the Definition of Done), completion over the work packages, and progress by branch.
  • WBS → Tree: the decomposition. Work packages carry their own status; each summary element's status is rolled up from the packages beneath it. Edit a node to write its WBS-dictionary entry and acceptance criteria.
  • WBS → Scope validation: every work package in WBS order with its criteria. Only a completed package can be accepted or rejected, and each decision records who signed.
  • Planning → Requirements and Traceability: each requirement's source, its forward traces to the WBS, and the backward trace: work packages that no requirement points to.
  • Planning → Scope: the governed scope statement and scope management plan.

Free downloads: Project scope statement template (Word, Markdown) · WBS template (Excel, CSV).

Walked example — Coral Ridge Resort

The WBS has 44 elements: the hotel (1), project management (1.1) and eight delivery phases in build order (1.2 design to 1.9 commissioning). Level 3 holds the 34 work packages, each with an acceptance criterion: "140 sea-view rooms finished to Corvane standard; no more than 3 snags per room at handover."

Mid-build, 8 work packages are complete. The owner has accepted three (the architectural design, the structural design and the site preparation). Five more, including the piling, are finished but still waiting for acceptance; the piling waits for the load-test reports its criterion names.

Seven requirements trace forward to the work. Tracing backward finds one package with no requirement: 1.8.2, hill-view terraces and gardens. Either the owner wants them and nobody wrote it down, or they are scope nobody asked for. Either way, the PM asks before the money is spent.

The workspace — the theory behind each screen

Every screenshot is the actual sample project, not a mock-up.


1 · The WBS: work packages and the 100% rule

The theory: decomposition. Break the scope down until each piece can be estimated, scheduled, assigned and accepted: the work package. Each level must add up to exactly its parent (the 100% rule), so nothing outside the scope statement sneaks in and nothing inside it is missed.

Coral Ridge — the WBS overview
Coral Ridge — the WBS overview

Reading the screenshot: the structure note explains the numbering and the Definition of Done: criteria met, checked by the site engineer, accepted by the owner. 34 work packages of 44 WBS elements: the other ten are the hotel and its phases, which are summaries, not work. Completion is counted over the packages (8 done = 24%), and By branch shows where the progress is: design 80%, site and substructure 67%, everything above ground still to come.

✅ Do stop decomposing when a package can be estimated and owned by one team.
❌ Avoid counting summary elements as work. A phase isn't "done" until its packages are.


2 · Summary elements roll up; work packages carry the status

The theory: the WBS is a hierarchy of deliverables. Status, cost and schedule are tracked on the work packages and summed upward. A summary element has no work of its own, so its status is derived, never typed in.

Coral Ridge — the WBS tree with rolled-up status
Coral Ridge — the WBS tree with rolled-up status

Reading the screenshot: the dashed pills on 1, 1.1, 1.2 and 1.3 are rolled up. 1.2 Design & Permits reads In Progress because four of its packages are done and the building permit (1.2.5) isn't. The work packages carry their own status, which the team updates. Edit opens the package's WBS-dictionary entry and its acceptance criteria.

✅ Do write acceptance criteria when you create the package, not when it's finished.
❌ Avoid marking a phase complete by hand while one of its packages is still open.


3 · Validate Scope: the customer accepts completed work

The theory: Validate Scope vs Control Quality. Control Quality is the team checking that a deliverable is correct. Validate Scope is the customer formally accepting it, against the agreed criteria. Quality control comes first: the inputs to Validate Scope are verified deliverables, and the outputs are accepted deliverables or change requests.

Coral Ridge — Scope validation
Coral Ridge — Scope validation

Reading the screenshot: each work package shows its criterion. 1.2.1 and 1.2.2 are Accepted, with who signed and why. 1.1.1, 1.1.2, 1.2.3 and 1.2.4 are complete and Ready for acceptance. 1.2.5 and 1.3.3 are still in progress, so there is no Accept button: VanillaPM won't let anyone accept work that isn't finished. The header counts it: 3 accepted, 5 ready, 26 not complete.

✅ Do accept each package against its written criterion, and record who signed.
❌ Avoid "accepting" a phase while one of its packages is still being built.


4 · Traceability: forward to the work, backward to a reason

The theory: the requirements traceability matrix. Each requirement is linked from its origin to the deliverables that satisfy it (forward trace), and each deliverable back to a requirement (backward trace). A requirement with no deliverable is a coverage gap; a deliverable with no requirement is either a missing requirement or gold plating: work added that nobody asked for.

Coral Ridge — the traceability matrix and backward trace
Coral Ridge — the traceability matrix and backward trace

Reading the screenshot: seven requirements, each with a source (the charter, the Corvane management agreement, the building code, CR-02 for the pool) and its work packages. Covered 7, gaps 0. The backward trace finds one untraced package: 1.8.2 Hill-view terraces & gardens. That's the question to take to the owner: write the missing requirement, or take the work out of scope.

✅ Do give every requirement a source and a way to verify it.
❌ Avoid treating untraced work as harmless. Unrequested work costs real time and money.

Best practices & pitfalls

  • Do decompose to work packages you can estimate, assign and accept: not so fine you drown in detail, not so coarse you can't control them.
  • Do keep the scope statement's exclusions explicit. They prevent most "I assumed that was included" arguments.
  • Do agree acceptance criteria before the work starts, and accept against them.
  • Pitfall: gold plating: adding features the customer didn't ask for. It is scope creep, even when well meant.
  • Pitfall: confusing a finished deliverable with an accepted one. Done is the team's call; accepted is the customer's.

On the PMP exam

Know the scope baseline (scope statement, WBS, WBS dictionary), the work package as the lowest WBS level, and the 100% rule. The classic trap is Validate Scope (formal acceptance, by the customer) versus Control Quality (correctness, by the team, and usually first). Know the RTM and that it traces requirements to deliverables and back. When a stakeholder asks for "just one more" feature, or a team member adds one unasked, the answer is the same: assess the impact and raise a change request. Scope changes without change control are scope creep.

Check your understanding a short quiz — pass to mark the task complete