UNDERSTAND THE CONCEPT
A work breakdown structure, or WBS, organizes project scope into a hierarchy of deliverables and manageable work packages. It helps teams agree what the project includes before building detailed schedules and cost controls. A useful structure covers the whole agreed scope without counting the same work twice. It is not simply an organization chart: responsibility can be assigned to the work after the scope boundaries are clear.
Give each work package a concise definition, an accountable owner and observable completion criteria. Include enabling work such as temporary facilities, testing, documentation and handover where these belong in scope. Codes should let teams connect estimates, commitments and actual costs to the same package. Avoid excessive detail that creates administration without improving decisions. If a package is too broad to estimate or assess objectively, decompose it further; if it is too small to manage meaningfully, reconsider the level of detail.
Questions to take back to your team
- Does the hierarchy cover all agreed deliverables without overlap?
- Can every work package be assigned and objectively completed?
- Do estimate and cost codes map to the same scope structure?
Further reading
Explore the primary references below. Requirements and applicability depend on your organization and jurisdiction.
