Insights

Work breakdown structure: how to build one, with an ERP example

A work breakdown structure turns a loose scope into a complete, numbered list of everything the project will deliver. Here are the rules that make one useful, a worked ERP example and a WBS dictionary template to copy.

By Christopher Fagan, Managing Partner, PEF Consulting Partners

£13bnlargest programme delivered
19 yrssenior systems delivery
5 continentsdelivered across
£25msaving on a single programme

Delivered for and alongside

ShellBPCapitaBaringaOfgemSmart DCCInsightsFlui TechnologiesExxonMobilVodafoneConstellation SoftwareDeloittePwCEYNational GridElexon

A work breakdown structure (WBS) is a numbered, hierarchical list of everything a project must deliver. It starts with the final outcome and splits it into smaller deliverables until each piece can be estimated, owned and tracked. The lowest items are called work packages, and together they make up the whole scope, with nothing missing and nothing extra.

A good WBS is the quiet foundation of a project. The schedule, the budget, the statement of work, the RACI and the risk log all hang off it. When it is wrong, everything built on it is wrong in the same place, and the gap usually surfaces late, as a change request nobody budgeted for.

What a WBS is, and what it is not

The WBS describes what will be delivered, not when it will happen or who will do it. It is not a schedule, although the schedule is built from it, and it is not an organisation chart, although each work package will have an owner. Nor is it a to do list. Activities such as ‘run design workshops’ sit beneath work packages in the plan, while the WBS itself names outcomes, such as ‘approved process designs’.

That distinction sounds pedantic until you try to control scope. A list of activities tells you people are busy. A list of deliverables tells you whether the thing you are paying for exists yet.

Where the WBS came from

The WBS grew up alongside PERT scheduling in the US defence and space programmes of the late 1950s and early 1960s. In 1962 the US military and NASA, working with the aerospace industry, published guidance for a combined schedule and cost control system that set out the work breakdown approach. A formal defence standard for work breakdown structures followed in 1968.

The core ideas have barely changed since. The usual modern reference is the Project Management Institute’s practice standard for work breakdown structures, which is where the 100 per cent rule is formally described.

The 100 per cent rule and the other rules that matter

The 100 per cent rule says the WBS must include all of the work in the project scope, and the elements at each level must add up exactly to their parent. If the children of an element do not cover all of it, work is missing. If they cover more, someone is doing work nobody asked for. The rule includes the work of managing the project, which is why most structures have a branch for it.

A few more rules keep a WBS usable in practice.

  • No overlaps. Each piece of work appears once. If two branches both contain data cleansing, one will be estimated twice and the other assumed to be someone else’s job.
  • Nouns, not verbs. Name outcomes, such as ‘trained users’ or ‘reconciled opening balances’, rather than activities.
  • Stop at the right depth. Decompose until a work package can be estimated with confidence and given to one accountable owner. A useful test is whether it can be finished within one or two reporting periods.
  • One owner per work package. Shared ownership tends to mean no ownership. A RACI matrix records who is responsible, accountable, consulted and informed.
  • Stable numbering. Codes such as 3.1.2 tie the WBS to the schedule, the cost ledger and the status report. Do not renumber once the baseline is set.

Deliverable based versus phase based

There are two common ways to organise the first level below the project. A deliverable based WBS puts the main products at the top: the configured system, the migrated data, the trained workforce. A phase based WBS puts lifecycle stages there instead, such as design, build, test and deploy, with deliverables underneath each one.

Phase based structures are easy to read and match how many delivery partners plan, so they are common on ERP programmes. Their weakness is that a single deliverable, such as data migration, gets scattered across four phases and nobody owns it from start to finish. Deliverable based structures make ownership and scope control clearer, and they map more cleanly to a statement of work when part of the delivery is contracted out.

Our preference on most programmes is deliverables at level 1, with the phases handled in the schedule. That is the approach used in the example below.

How to build a WBS in six steps

  1. Start from agreed scope. Build the WBS from the approved scope in the project charter or business case, not from memory. If the scope is not agreed, the first workshop will expose that quickly, which is useful in itself.
  2. Name the final product. This is level 0, for example ‘new finance system live and adopted’.
  3. Choose the level 1 split. Deliverable or phase based, as above, plus a branch for managing the project.
  4. Decompose each branch. For every element, ask what has to exist for it to be complete, and keep going until you reach work packages one person can own and estimate.
  5. Test against the 100 per cent rule. Walk each branch with the people who will do the work and ask what is missing. Integrations, reporting, decommissioning and training for support teams are the usual gaps.
  6. Write the WBS dictionary and baseline it. Record what each work package includes, what it excludes and how it will be accepted, then put the structure under change control. From here it becomes the backbone of the project plan and the project initiation document.

Work breakdown structure example: a hypothetical ERP implementation

This example is invented for illustration. It shows a mid sized distribution business replacing its finance and supply chain systems with a cloud ERP. It is deliverable based and taken to a third level in one branch only, to keep it readable; a real ERP structure would run to many more work packages.

WBS codeElementWhat it covers
1.0Programme managementGovernance, planning, reporting and supplier management
1.1    Governance and reportingSteering group, terms of reference, monthly status reports
1.2    Integrated plan and RAID logBaseline schedule, risks, assumptions, issues and dependencies
1.3    Commercial managementSupplier contracts, change control, supplier performance
2.0Solution designApproved future processes and system design
2.1    Future process designsRecord to report, procure to pay, order to cash, inventory
2.2    Chart of accounts and reporting designNew coding structure, management and statutory reports
2.3    Integration and data designInterface list, data model, migration scope
3.0Configured systemERP configured and built to the approved design
3.1    Finance configurationCore finance modules
3.1.1        General ledgerEntities, chart of accounts, periods, consolidation
3.1.2        Payables and receivablesSupplier and customer accounts, payment runs, credit control
3.1.3        Fixed assetsAsset classes and depreciation rules
3.2    Supply chain configurationPurchasing, inventory, warehousing, sales orders
3.3    IntegrationsPayroll, banking, CRM and ecommerce interfaces
3.4    Reports and dashboardsBuilt to the design in 2.2
4.0Migrated dataClean, reconciled data loaded into the new system
4.1    Cleansed source dataDuplicates removed, obsolete records archived
4.2    Mapping and transformation rulesField level mapping approved by data owners
4.3    Trial loads and reconciliationRehearsal loads with balances and record counts agreed
4.4    Final loadProduction load and finance approval of opening balances
5.0Tested solutionEvidence that the system works and is accepted
5.1    System and integration testingEnd to end scenarios across modules and interfaces
5.2    User acceptance testingBusiness led testing and formal acceptance
5.3    Performance and security testingVolume tests, user roles and access controls
6.0Business readinessPeople and processes ready to run on the new system
6.1    Trained usersMaterials, sessions and super users in each area
6.2    Procedures, roles and controlsDesk instructions, approval limits, segregation of duties
6.3    CommunicationsMessages for staff, customers and suppliers
7.0Live serviceSystem in use and supported
7.1    CutoverCutover plan, rehearsals and the go or no go decision
7.2    HypercareExtra support for the first weeks after go live
7.3    Support handover and decommissioningSupport model in place, legacy system archived and switched off

Three choices in this example are worth copying. Data migration is a level 1 deliverable with its own owner rather than a task inside the build, because it is one of the riskiest parts of any ERP programme; our piece on what goes wrong with ERP data migration explains why. Business readiness sits alongside the technical branches, so training and process change are estimated from day one rather than squeezed in at the end. And decommissioning the old system is in scope, which is the piece of work most often forgotten.

How these deliverables are then sequenced across the programme is covered in our ERP implementation plan guide.

A work breakdown structure template and WBS dictionary

The outline shows the structure. The WBS dictionary holds the detail behind each work package, and it is the part that settles scope arguments later. Paste the table into a spreadsheet, give each work package its own row and use the example column as a guide.

FieldWhat to recordExample for 4.3
WBS codeThe unique code from the outline4.3
Work packageThe deliverable, written as a nounTrial loads and reconciliation
DescriptionWhat the package producesTwo rehearsal loads of master data and open balances, each reconciled to the legacy system
IncludesWork that is in scopeLoad scripts, reconciliation reports, fixes to mapping rules
ExcludesWork that is explicitly out of scopeMigration of closed transactions older than two years
OwnerOne accountable personData migration lead
Acceptance criteriaHow everyone will know it is doneBalances agree to the penny, record counts within agreed tolerance, sign off by the financial controller
EstimateEffort and cost, with the basisEffort in days by role, with assumptions stated
DependenciesWhat it needs from other packages4.2 mapping approved, 3.1 configuration complete
Risks and assumptionsAnything that could change the estimateLegacy extract available on time, data owners free to review results

Keep the dictionary short enough that people actually read it. A line or two per field is plenty for most work packages, while the ones with commercial or regulatory weight deserve more.

Common mistakes

  • Building it backwards from a schedule. A WBS that tidies up an existing Gantt chart inherits every gap in that chart.
  • Organising by department. Structures that mirror the organisation chart hide the handoffs between teams, which is where work tends to fall through.
  • Going too deep. Hundreds of tiny work packages create reporting overhead and false precision. That level of detail belongs in the schedule.
  • Leaving out the unglamorous work. Managing the project, test environments, data cleansing, training, decommissioning and hypercare are routinely missed.
  • No dictionary. A one line element name means different things to the client, the supplier and the finance team.
  • No baseline. If the WBS changes without change control, the scope has changed without anyone deciding that it should.

How the WBS connects to the rest of delivery

Once the work breakdown structure is baselined, everything else plugs into it. Work packages are broken into activities, sequenced and estimated, and critical path analysis shows which of those activities set the end date. Costs roll up by WBS code, so budget and actuals can be compared at any level, and status reports, risks and change requests all refer back to the same codes.

On public sector schemes, a credible WBS and plan also feed the management case of a Five Case Model business case, where reviewers want evidence that the proposal can actually be delivered.

Christopher Fagan’s finance system work over 19 years spans Microsoft Dynamics, SAP S/4HANA, Oracle, Unit4, NetSuite, Sage and Access, and the shape of a sound ERP structure changes surprisingly little between them. On the National Grid separation, Christopher Fagan led the purchase of every software system right through to implementation, which is exactly the kind of programme where scope has to be split cleanly between suppliers and their statements of work.

Common questions

What is a work breakdown structure?

A work breakdown structure is a hierarchical list of everything a project has to deliver. It starts with the final outcome and divides it, level by level, into smaller deliverables until each piece is small enough to estimate, assign to one owner and track. The lowest level pieces are called work packages, and together they should cover the whole scope and nothing else.

What is the 100 per cent rule in a WBS?

The 100 per cent rule says a work breakdown structure must include all of the work in the project scope and nothing outside it. At every level, the child elements must add up to exactly their parent. If they fall short, work is missing from the plan and the budget. If they go beyond it, effort is being spent on things nobody agreed to deliver.

What is a WBS dictionary?

A WBS dictionary is the document behind the WBS outline that describes each work package in detail. It usually records the code, a description, what is included and excluded, the owner, acceptance criteria, estimates, dependencies and key assumptions. It stops a short element name meaning different things to the client, the supplier and the finance team, and it is the first place to look when scope is disputed.

What is the difference between a deliverable based and a phase based WBS?

A deliverable based WBS puts the main products of the project at level 1, such as the configured system, migrated data and trained users. A phase based WBS puts lifecycle stages there instead, such as design, build, test and deploy. Phase based structures are easy to follow, but deliverable based ones make ownership and scope control clearer, especially when work is contracted out.

How many levels should a work breakdown structure have?

Most projects need three or four levels. Keep breaking the work down until each work package can be estimated with confidence, given to one accountable owner and finished within one or two reporting periods. Going further adds reporting overhead without adding control. Large programmes may need more levels overall, but each project within them should still stop at a manageable depth.

Related reading: Critical path analysis, ERP implementation plan, Project plan template and Statement of work template.

Not sure your scope is complete?

We can test your work breakdown structure and plan against the 100 per cent rule before you commit to a budget or a supplier, then help your team close the gaps.

Book a confidential conversation

Sources: Project Management Institute, Practice Standard for Work Breakdown Structures, second edition, 2006; Haugan, G. T., Effective Work Breakdown Structures, 2002

PEF TRACK RECORD£13bnLargestprogramme led5Continentsdelivered across19 yrsSystems delivery£25mLargestsingle saving
CF

Written by Christopher Fagan

Managing Partner, PEF Consulting Partners

Christopher has led systems and transformation delivery for 19 years, including the National Grid separation, the £9bn Energy Bills Support Scheme and the BP Pulse EV charging rollout.