Work Breakdown Structures and Activity Definition

The decision: what exactly are we planning?Source §Work breakdown · Decision-led opening

A schedule cannot control scope that has not been defined. If packages overlap, omit temporary work, mix deliverables with actions or use vague completion rules, durations and logic will inherit those defects. A work breakdown structure creates a controlled view of the project scope. Activity definition then converts ready work packages into observable work that can be sequenced, resourced, measured and accepted.

Prerequisite checkSource §Learning sequence · Prior knowledge

Use decomposition to make scope governableSource §Work breakdown · Purpose of decomposition

Decomposition divides the authorised project scope into progressively smaller deliverables until the team reaches a level that can be assigned, estimated, planned, risk-reviewed and controlled. The objective is not maximum detail. The objective is sufficient definition for reliable decisions while maintaining a traceable path back to the approved project outcome.

Deliverable

A verifiable product, result or capability that contributes to the authorised project scope.

Work breakdown structure

A hierarchical decomposition of the complete project scope into controlled deliverables and work packages.

Work package

A lowest controlled WBS component that can be assigned, estimated, planned, risk-reviewed and measured.

Planning package

Authorised scope held at a higher level until sufficient information exists for detailed work-package definition.

Activity

A measurable piece of work with a duration, logic relationships and an observable completion condition.

Milestone

A zero-duration event marking an approval, hand-off, acceptance or other control point.

Apply the hundred-percent rule and prevent overlapSource §Work breakdown · Completeness rules

Each parent element should be fully represented by its children: no missing authorised scope and no extra scope. Sibling elements should be mutually distinguishable so responsibility, quantities, cost and progress are not counted twice. The sum is conceptual rather than merely numeric; temporary works, approvals, testing, information and handover evidence still need an explicit home.

• Start from the latest authorised scope and documented exclusions.
• Choose a primary decomposition logic at each branch, such as system, asset, zone or deliverable stage.
• Test every parent against the combined children and every sibling against overlap.
• Give temporary works, logistics, testing, permits, commissioning, information and handover an explicit control location.
• Record unresolved scope as an owned planning package or assumption—not as silence.
• Freeze and change-control WBS codes once downstream systems rely on them.

Code once and map many control viewsSource §Control coding · Coding architecture

A stable WBS code identifies the scope element. Separate attributes can identify location, organisation, cost account, contract package, information container, risk owner and schedule activity. Combining every attribute into one fragile code makes restructuring difficult and encourages users to infer responsibility from the wrong field.

Define a work package before releasing activitiesSource §Work packages · Work-package definition

A work package is ready for detailed planning when the team can state what is included and excluded, who is accountable, how completion will be accepted, what quantity or completion rule will measure progress, which interfaces control it, and which information or constraints are required. A package may be conditionally released only through an authorised and traceable decision.

Translate the package into measurable activitiesSource §Activity definition · Scope-to-activity translation

Activities describe the work required to create and accept the package deliverable. They should be specific enough to estimate duration, assign resources, connect credible logic and measure progress. An activity name is strongest when it combines an action, object and useful location or work-front qualifier.

• Use one observable completion condition rather than an open-ended level of effort where possible.
• Keep duration consistent with quantity, productivity, crew, access and calendar assumptions.
• Connect each non-start activity to a credible predecessor and each non-finish activity to a successor.
• Represent approvals and hand-offs as milestones only when they genuinely consume no planned duration.
• Split an activity when different work fronts, responsibilities, calendars, logic or progress rules must be controlled separately.
• Avoid splitting merely to create detail that nobody will update or use.

Define duration and progress from the same scope basisSource §Activity definition · Duration and progress basis

Worked decomposition: external envelopeSource §Worked example · Envelope decomposition

Predict and test work-package readinessSource §Interactive learning · Readiness explorer

The explorer begins with only a package boundary and accountable owner. Predict the gate state, add evidence, then inspect whether the package is ready, conditionally ready or still in development. Critical scope, ownership and acceptance criteria cannot be compensated for by a high total score.

Audit the breakdown before baseline approvalSource §Schedule quality · WBS quality review

• Trace every activity to one controlled work package and every work package to authorised scope.
• Test parent-child completeness and sibling overlap at every material branch.
• Confirm planning packages have owners, assumptions and decomposition dates.
• Check that responsibilities, cost accounts, locations and information containers map without altering scope identity.
• Verify activity names, completion rules, quantities, calendars, logic and progress sources.
• Search explicitly for temporary works, logistics, testing, permits, commissioning, training and records.
• Record review evidence, changes and approval authority.

Applied learning taskSource §Assessment · WBS assignment