Insights
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
Delivered for and alongside
















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.
In this article
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.
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 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.
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.
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 code | Element | What it covers |
|---|---|---|
| 1.0 | Programme management | Governance, planning, reporting and supplier management |
| 1.1 | Governance and reporting | Steering group, terms of reference, monthly status reports |
| 1.2 | Integrated plan and RAID log | Baseline schedule, risks, assumptions, issues and dependencies |
| 1.3 | Commercial management | Supplier contracts, change control, supplier performance |
| 2.0 | Solution design | Approved future processes and system design |
| 2.1 | Future process designs | Record to report, procure to pay, order to cash, inventory |
| 2.2 | Chart of accounts and reporting design | New coding structure, management and statutory reports |
| 2.3 | Integration and data design | Interface list, data model, migration scope |
| 3.0 | Configured system | ERP configured and built to the approved design |
| 3.1 | Finance configuration | Core finance modules |
| 3.1.1 | General ledger | Entities, chart of accounts, periods, consolidation |
| 3.1.2 | Payables and receivables | Supplier and customer accounts, payment runs, credit control |
| 3.1.3 | Fixed assets | Asset classes and depreciation rules |
| 3.2 | Supply chain configuration | Purchasing, inventory, warehousing, sales orders |
| 3.3 | Integrations | Payroll, banking, CRM and ecommerce interfaces |
| 3.4 | Reports and dashboards | Built to the design in 2.2 |
| 4.0 | Migrated data | Clean, reconciled data loaded into the new system |
| 4.1 | Cleansed source data | Duplicates removed, obsolete records archived |
| 4.2 | Mapping and transformation rules | Field level mapping approved by data owners |
| 4.3 | Trial loads and reconciliation | Rehearsal loads with balances and record counts agreed |
| 4.4 | Final load | Production load and finance approval of opening balances |
| 5.0 | Tested solution | Evidence that the system works and is accepted |
| 5.1 | System and integration testing | End to end scenarios across modules and interfaces |
| 5.2 | User acceptance testing | Business led testing and formal acceptance |
| 5.3 | Performance and security testing | Volume tests, user roles and access controls |
| 6.0 | Business readiness | People and processes ready to run on the new system |
| 6.1 | Trained users | Materials, sessions and super users in each area |
| 6.2 | Procedures, roles and controls | Desk instructions, approval limits, segregation of duties |
| 6.3 | Communications | Messages for staff, customers and suppliers |
| 7.0 | Live service | System in use and supported |
| 7.1 | Cutover | Cutover plan, rehearsals and the go or no go decision |
| 7.2 | Hypercare | Extra support for the first weeks after go live |
| 7.3 | Support handover and decommissioning | Support 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.
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.
| Field | What to record | Example for 4.3 |
|---|---|---|
| WBS code | The unique code from the outline | 4.3 |
| Work package | The deliverable, written as a noun | Trial loads and reconciliation |
| Description | What the package produces | Two rehearsal loads of master data and open balances, each reconciled to the legacy system |
| Includes | Work that is in scope | Load scripts, reconciliation reports, fixes to mapping rules |
| Excludes | Work that is explicitly out of scope | Migration of closed transactions older than two years |
| Owner | One accountable person | Data migration lead |
| Acceptance criteria | How everyone will know it is done | Balances agree to the penny, record counts within agreed tolerance, sign off by the financial controller |
| Estimate | Effort and cost, with the basis | Effort in days by role, with assumptions stated |
| Dependencies | What it needs from other packages | 4.2 mapping approved, 3.1 configuration complete |
| Risks and assumptions | Anything that could change the estimate | Legacy 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.
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.
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.
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.
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.
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.
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.
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
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.
Where next