First, the key terms.

Deliverable
A verifiable output or capability to be accepted.
Work package
A manageable component at the chosen lower level of a WBS.
Acceptance criterion
A condition used to judge whether a result meets its purpose.

The idea, explained

A scope statement makes boundaries and acceptance criteria visible. A WBS answers what must be delivered, rather than when every task happens or who reports to whom. Work packages provide a basis for estimating, scheduling and responsibility assignment. Requirements, scope and a schedule are connected but different. Change control evaluates a proposed alteration’s impact before changing the agreed plan. Communication supports those decisions by reaching the right audience with information they can use, not by producing the maximum number of status messages.

STEP 1

Define inclusion and exclusion

For a newsletter, state whether email preferences, payments, audio and a learning library are included. “Build the platform” hides those choices. Include data, testing, security and handover work that users do not directly see.

STEP 2

Decompose without losing work

Break the scope into deliverables whose combined coverage represents the agreed project. Avoid duplicating the same work under several branches. Estimate only after the team understands what each package actually contains.

STEP 3

Communicate changes as decisions

A new request should identify its benefit, effort, dependencies and risk. Tell the sponsor what commitment would change and who must approve it. Tailor progress reports: executives need decisions and impacts; implementers need actionable detail.

Follow a worked example.

An AI support pilot includes a labeled dataset, a routing service, a review interface and operational handover. “Train model” is insufficient as the whole WBS because it excludes the workflow that makes the prediction useful.

Walk it through, one step at a time

  1. Give each deliverable an acceptance owner and measurable conditions. A review interface must handle ambiguous and failed cases, not merely display a score.
  2. Derive activities and dependencies from the packages. The WBS itself is not yet the time-ordered schedule.
  3. A request for multilingual support adds labeling and evaluation work. Review that impact before silently adding it to the promised launch.

Where people get stuck

A polished WBS cannot compensate for missing requirements or acceptance criteria that measure only technical completion.

Now try it yourself.

Pause before opening each answer. Explain your reasoning in your own words.

1. Check the core idea

How does a WBS differ from a schedule?

Reveal the answer & reasoning

The WBS organizes scope into deliverables and work packages. A schedule adds activities, durations, sequencing and resource-related timing.

2. Apply what you learned

A sponsor asks for another feature “because the team is already working on that screen.” What should be checked?

Reveal the answer & reasoning

Check the actual data, implementation, testing and support impact. Nearby interface placement does not establish that the change is small or already included.