The worst work breakdown construction instance I ever inherited was a 47-page doc produced by a planning advisor in the beginning of a serious fit-out programme. It was technically spectacular. Degree 1, degree 2, degree 3, degree 4, work packages right down to two-hour duties. The mission supervisor had by no means checked out it after the kick-off assembly. The workforce had no concept it existed. After I requested why, the reply was instant: “It doesn’t replicate how we really work.” The WBS had been constructed by the advisor in a two-week planning engagement, reviewed by the consumer’s business workforce for contractual compliance, and filed. The supply workforce had by no means seen it. In the meantime the mission was working off a shared Excel workbook that the positioning supervisor had constructed throughout the first week — no formal hierarchy, inconsistent naming, tabs labelled issues like “M+E stuff” and “week 3 priorities.” Genuinely helpful. The WBS: good, full, and untouched.
That hole — between a WBS that satisfies a strategy requirement and one that truly drives planning and management — is what this text is about.
What a Work Breakdown Construction Really Is — and What It Isn’t
A work breakdown construction in mission administration is a hierarchical decomposition of all of the work the mission should ship. Not all of the actions. Not the schedule. The deliverables — the issues that have to exist when the mission is completed, damaged right down to a degree the place they are often deliberate, estimated, assigned and managed.
Most planners know this in concept. In observe, phase-based WBS constructions are in every single place. On the second WBS evaluation I did on a business refurbishment programme, each degree 2 component was a section: “design section,” “procurement section,” “building section.” Tidy. Logical. Utterly ineffective for scope management, as a result of when a consumer asks whether or not structural strengthening is included, “building section” doesn’t let you know. A deliverable-oriented WBS would have “structural body” as a degree 2 component and structural strengthening both explicitly inside or outdoors it. Actions change consistently because the mission evolves; deliverables are extra steady — they describe what the mission produces, not the way it does it.
PMBOK’s definition focuses on work packages — the bottom degree of the WBS, the place scheduling, value estimating and management occur. Work packages aren’t job lists. They’re accountability models. One proprietor, a transparent definition of accomplished, verifiable completion. In observe the excellence between “work bundle” and “exercise” will get blurred consistently — scheduling software program doesn’t care, and plenty of groups skip the WBS totally and go straight to the exercise listing. The initiatives the place this causes probably the most hassle are those the place scope grows via permitted modifications and no one can inform anymore what was within the unique mission and what was added.
The commonest confusion: WBS and schedule aren’t the identical doc. A schedule exhibits when issues occur and in what sequence. A WBS exhibits what the mission produces, organized by deliverable hierarchy. Utilizing one instead of the opposite is a scope management downside ready to occur — I’ve reviewed initiatives the place the “WBS” was a Gantt chart organised by section, and when disputed variations arrived, no one might reply the elemental query: was this in scope or not? The Gantt informed you the sequence. It informed you nothing about scope boundaries.
Learn how to Construct a WBS That Will get Used
Begin on the high — with what the mission has to provide — and work downward. Not from an inventory of duties constructed bottom-up, as a result of that produces a schedule or a job listing fairly than a scope construction. High-down decomposition begins with the end-state and asks: what are the foremost issues that have to exist for this mission to be full? Every of these turns into a degree 2 component. Then for every degree 2 component, the identical query: what sub-deliverables does this decompose into? Preserve going till you attain one thing estimable, assignable and verifiable.
Begin with the ultimate deliverable
Degree 1 of each WBS is the mission itself. One field. One title. The whole lot else flows from it. This appears trivially apparent but it surely forces one thing essential: settlement on what the mission really is. I’ve began WBS periods the place the room couldn’t agree on what went within the degree 1 field, which meant we had been doing scope definition that ought to have occurred earlier than the WBS.
Determine the foremost deliverable teams
Degree 2 is a very powerful degree. These are the foremost chunks the mission produces — not phases, not departments, not actions. Deliverables. On a constructing mission: construction, envelope, fit-out, MEP companies, exterior works, commissioning. On a software program mission: necessities, structure, developed system, examined system, deployed system, documentation. On an occasion: venue, content material programme, logistics, communications, staffing.
Getting degree 2 proper means the WBS is usable as a scope map. Getting it unsuitable — through the use of phases or organisational models as an alternative of deliverables — produces a construction that’s arduous to keep up, as a result of what occurs when a section is “accomplished” however the deliverable it was supposed to provide isn’t? The WBS stops reflecting actuality and will get deserted.
Decompose to work packages
Preserve decomposing every degree 2 component till you attain work packages — models of labor that may be estimated, assigned and tracked. A piece bundle has: one accountable particular person or workforce, a transparent definition of accomplished (what does “full” imply for this bundle?), an estimated value and length, and a verifiable output. When you can’t outline what “accomplished” seems like for a WBS component, it’s not a piece bundle but. Preserve decomposing.
Construct it with the individuals who’ll do the work
I’ve by no means seen it accomplished in isolation that was proper. Not as soon as. Not unsuitable in small methods — unsuitable in ways in which solely the individuals doing the work might learn about. On a civils mission: the planning engineer decomposed “groundworks” into 4 work packages with out figuring out that the geotechnical report had flagged a floor stability constraint that made two of these packages sequential fairly than parallel. The constraint was recognized. It simply wasn’t within the room when the WBS was constructed. 4 weeks in: an 8-week slip. Solely predictable. From data that already existed.
Work Breakdown Construction Instance: Building Mission
A work breakdown construction in building is usually deliverable-oriented, reflecting the bodily parts of the construction fairly than the commerce sequence or the programme phases. That is the excellence that skilled building planners get proper and inexperienced ones typically don’t: the WBS construction ought to stay steady even because the programme modifications.
Under is a piece breakdown construction instance for a business workplace fit-out mission, Degree 1–3:
| Degree 1 | Degree 2 | Degree 3 (Work Packages) |
|---|---|---|
| Workplace Match-Out Mission | Structural alterations | Slab penetrations · Stair cores · Structural metal |
| Constructing material | Raised flooring · Suspended ceilings · Partitions · Glazing | |
| M+E companies | Electrical distribution · Lighting · HVAC · IT infrastructure · Hearth detection | |
| Match-out | Kitchen/break areas · WC fitout · Reception · Furnishings set up | |
| Commissioning | Programs commissioning · Snagging · Handover documentation |
An actual building WBS failure — and what it value
On a hospital extension mission I reviewed mid-delivery, the WBS had been structured by section fairly than by deliverable. Degree 2 parts had been “design stage,” “procurement stage,” “building stage,” “commissioning stage.” Clear, logical, and a scope management catastrophe. When variations began arriving — from the consumer, from the statutory authority, from floor situation discoveries — no one might say with certainty whether or not a selected variation was inside current scope or outdoors it, as a result of “building stage” might imply nearly something. By the point I used to be it, the mission had processed 43 variations. Fourteen had been disputed. The foundation trigger of each disputed variation was traceable to the identical factor: a WBS that described time fairly than deliverables, which made it unattainable to say with any precision what the unique scope contained.
The repair was to rebuild the WBS deliverable-by-deliverable retrospectively — which took three weeks, concerned the amount surveyor, the mission supervisor and the consumer’s consultant, and produced a doc that everybody agreed described the unique scope. It additionally confirmed that 4 of the disputed variations had been in scope all alongside. One was genuinely further. The remaining: genuinely disputed. Official causes on either side. That three-week train would have taken three days in the beginning. It all the time does.
Two issues intentionally absent from this construction: procurement and mission administration. Procurement isn’t a deliverable — it’s a course of that produces the bodily parts listed above. Mission administration is overhead. Neither ought to seem as a WBS department in a deliverable-oriented construction. Dates and sequences are additionally absent — these belong within the programme. The WBS feeds the programme; it doesn’t comprise it.
The place the work breakdown construction in building genuinely earns its hold is in scope management conversations. When a consumer asks whether or not “good constructing controls” is included within the mission, the reply ought to come from the WBS. Both “IT infrastructure” beneath M+E companies covers it, or it doesn’t, and it must be added as a piece bundle with its personal value and programme implications. The WBS makes that dialog concrete fairly than obscure.
Work Breakdown Construction Instance: Software program Mission
Software program initiatives produce a unique sort of WBS than building, partly as a result of the deliverables are much less tangible and partly as a result of agile improvement has made some groups skeptical of WBS altogether. The skepticism is partly warranted — a WBS for a software program mission shouldn’t be decomposed to particular person person tales, which belong within the product backlog, not the WBS. However the mission nonetheless must outline its scope at a degree above the backlog, and that’s what the WBS is for.
A work breakdown construction instance for a software program improvement mission — enterprise CRM system alternative, roughly 18 months:
| Degree 2 deliverable | Degree 3 work packages |
|---|---|
| Necessities | Enterprise necessities doc · Knowledge migration specification · Integration necessities · Non-functional necessities |
| System design | Structure design · Database schema · API specification · Safety design · Infrastructure design |
| Developed system | Core CRM modules · Buyer knowledge migration · Third-party integrations · Reporting module · Admin portal |
| Examined system | Unit take a look at suite · Integration take a look at outcomes · UAT-ready construct · Efficiency take a look at report · Safety audit report |
| Deployed system | Manufacturing setting · Deployment runbook · Rollback process · Go-live sign-off |
| Enablement | Consumer coaching supplies · Administrator documentation · Help handover · Submit-go-live help interval |
The “examined system” and “deployed system” are separate deliverables on this WBS as a result of they’re separate issues with separate house owners and separate acceptance standards. A standard mistake on software program initiatives is collapsing testing into improvement — making “examined system” a sub-element of “developed system.” This nearly all the time produces insufficient take a look at protection as a result of testing will get squeezed when improvement runs over, which it practically all the time does. The WBS ought to replicate what you wish to be true, not simply what tends to occur.
What’s not on this WBS: mission administration. PMBOK permits it as a department. I’d reduce it. Mission administration is overhead; it doesn’t produce a deliverable that the consumer receives and accepts. If the contract requires PM deliverables — execution plans, month-to-month reviews, danger registers — these can sit beneath a “mission controls” department. However “mission administration effort” as a WBS component inflates the construction with out including scope readability.
Work Breakdown Construction Instance: Occasion Administration
Occasion administration WBS constructions are helpful as a result of they illustrate how the decomposition precept works in a non-technical, high-dependency setting. The whole lot about an occasion is interconnected — change one component and you alter a number of others — which makes scope readability notably essential.
Under is a work breakdown construction instance for a 500-person skilled convention, damaged to Degree 3:
| Degree 2 | Degree 3 work packages |
|---|---|
| Venue | Predominant auditorium · Breakout rooms · Catering areas · AV setup · Signage and wayfinding |
| Content material programme | Keynote periods · Workshop programme · Panel discussions · Speaker briefing packs · Session recordings |
| Logistics | Delegate registration system · Lodging block · Transport preparations · On-site staffing · Occasion app |
| Communications | Delegate invites · Speaker communications · Sponsor supplies · Social media content material · Submit-event report |
| Industrial | Sponsorship packages · Delegate ticket gross sales · Exhibition area · Finances reconciliation |
The worth of constructing this WBS earlier than detailed planning begins: it surfaces dependencies. “Occasion app” beneath logistics connects to “delegate registration system,” “session recordings” beneath content material, and “social media content material” beneath communications. Earlier than you’ve deliberate any of it, you may see that these 4 work packages have to be coordinated. With out the WBS, every could be deliberate in isolation and the connections would solely emerge as issues.
What Makes a Work Breakdown Construction Fail
Exercise-oriented as an alternative of deliverable-oriented
The commonest structural error. “Conduct web site surveys,” “maintain design workshops,” “full procurement” — these are actions. They’re helpful in a schedule. In a WBS they make scope management unattainable, as a result of actions finish however the deliverables they had been supposed to provide might not exist but. A WBS constructed on actions tends to be deserted throughout execution as a result of no one can inform from it whether or not the mission is on scope.
Too many ranges
The WBS that goes to Degree 6 on a six-month mission. Every work bundle is 2 days of effort. The PM spends extra time sustaining the WBS than delivering the mission. The 8/80 rule — work packages between 8 and 80 hours — exists for a motive. Under 8 hours you’re micromanaging. Above 80 hours the bundle is simply too giant to trace meaningfully. Most initiatives are properly served by three or 4 ranges, with some branches going deeper the place complexity calls for it.
Constructed as soon as and by no means up to date
The WBS is a residing doc. When scope modifications are permitted via change management, the WBS ought to replicate them. I’ve reviewed initiatives the place the WBS was produced at planning and by no means touched once more — whereas the scope grew considerably via permitted modifications. The WBS confirmed the unique scope. The programme, the associated fee reviews and the workforce’s precise workload confirmed one thing else. That hole makes mission reporting unreliable and makes it very arduous to find out after the very fact whether or not overruns had been brought on by scope progress or by poor efficiency.
No WBS dictionary
The WBS diagram alone is ambiguous. “Basis works” in a building WBS — does that embody piling? Momentary works? De-watering? The WBS dictionary supplies a definition for every component: what’s included, what’s excluded, acceptance standards, assumptions. With out it, two individuals can take a look at the identical WBS component and assume completely different scope. The dictionary converts the visible construction right into a contract with the workforce about what the mission will produce.
How Many Ranges Is Sufficient?
The choice rule: decompose to the extent the place you may reliably estimate value and length, assign clear accountability, and outline what “accomplished” seems like. Cease. That degree varies by mission and by department inside a mission — some parts want 4 ranges, some want two. The WBS doesn’t need to be symmetrical.
On a three-month inner IT mission, three ranges might be sufficient. On a serious infrastructure programme working 5 years, 4 or 5 ranges could be wanted in some branches whereas three is ample in others. The WBS doesn’t need to be symmetrical — not each department wants the identical depth. What issues is that each work bundle on the lowest degree of every department meets the three standards: estimable, assignable, verifiable.
A helpful take a look at: take any component in your WBS and ask whether or not the particular person chargeable for it might let you know when it’s accomplished, what it will value to do, and who’s doing it. If the reply to any of these is “I’d want to speak to another person first,” the component must be decomposed additional or the obligations clarified.
WBS within the PMP Examination
The PMP and CAPM exams take a look at WBS primarily via questions on decomposition, work packages, and the WBS dictionary. Situation questions usually ask you to determine what belongs in a WBS versus what belongs in different paperwork, or to recognise when a WBS is being constructed incorrectly.
Key factors for examination functions: the WBS represents 100% of the mission scope — nothing is completed on the mission that isn’t within the WBS, and every thing within the WBS is a part of the mission. The bottom degree of the WBS is the work bundle. Work packages are deliberate into schedule actions, however actions aren’t the identical as work packages. The WBS dictionary defines every component. The WBS is an enter to value estimating, schedule improvement, danger identification and useful resource planning — it’s not an output of these processes.
For associated scope administration ideas, see the articles on mission life cycle phases and mission danger administration. The PMI PMBOK Information covers WBS building and the WBS dictionary within the scope administration information space.
Victor Z Younger is a Civil Engineer with 35 years of expertise working alongside the chief workforce of assorted building firms. Victor makes a speciality of building insurance coverage, delay evaluation, efficiency evaluation and engineering. He holds a Physician of Mission Administration from Northwestern College.