Ask a project team to plan and most people start listing activities: design, order, build, test. The list grows, overlaps and never adds up to the result.
A work breakdown structure starts from the other end. It asks what must exist when the project is finished, and breaks that result down until each piece can be owned.
Four levels
For a new assembly cell the structure looks like this:
- Level 1, project: assembly cell B.
- Level 2, deliverables: mechanical design, electrical design, software, procurement, build and commissioning, training and handover, project management.
- Level 3, work packages: for software, for example requirements, PLC program, operator interface, test and release.
- Level 4, activities: only where the owner of a work package needs them, planned by that owner.
Use deliverables, not departments. A structure built around departments breaks with the next reorganization and hides the work between them.
The 100 percent rule
The children of every element add up to the parent, nothing more and nothing less. If the cell needs a safety concept and nobody’s package contains it, the gap appears at the acceptance test.
Project management itself is a deliverable. Planning, meetings, reporting and documentation take time, often 5 to 10 percent of the effort. Give them a package and a budget.
One card per work package
A work package is the contract between the project manager and its owner. It fits on one card:
- owner, one name,
- content, what the package produces,
- input needed and from whom,
- definition of done, one sentence that can be checked,
- estimate and budget.
“PLC program tested on the simulation model, all 48 test cases passed, code reviewed” is a definition of done. “Software finished” is not.
Packages of 40 to 400 hours work well. Smaller ones create administration, larger ones hide problems for months.
One number everywhere
Number the structure once and use the same numbers in the schedule, the cost plan, the RACI, the risk register and the status report. When the steering committee asks about package 3.2, everybody looks at the same thing.
Build it with the team
The best work breakdown is built on a wall in two hours with the people who will do the work. Deliverables on yellow notes, work packages on blue notes below, owners written on each.
The team finds the gaps faster than any project manager alone, and owners who wrote their own package rarely say later that it was never theirs.