Infrastructure Development Work Breakdown Structure
This is a practical guide to building a work breakdown structure for an infrastructure development project — a deliverable-oriented decomposition of the whole scope into manageable work packages, adapted to the realities of delivering large public or private infrastructure.
What a Work Breakdown Structure is
A work breakdown structure is a deliverable-oriented decomposition of the whole scope into manageable work packages. For the full concept and how it works in general, see Work Breakdown Structure. On an infrastructure development project it plays the same role, tuned to this kind of work.
Why it matters for an Infrastructure Development project
Infrastructure Development projects live or die on delivering large public or private infrastructure. A well-built work breakdown structure gives the team a shared, explicit reference for exactly that — reducing ambiguity, aligning stakeholders, and making problems visible early enough to act. Skipping it, or doing it generically, is how infrastructure development projects drift into avoidable delay and cost.
What to include
- Top-level deliverables
- Sub-deliverables
- Work packages (8–80 hours)
- WBS numbering
- WBS dictionary entries
Infrastructure Development-specific considerations
Tailor the work breakdown structure to the risks that most often derail infrastructure development projects:
- Long lead times
- Permits and land
- Cost inflation over long horizons
Example
On a real infrastructure development project, the work breakdown structure would be shaped by delivering large public or private infrastructure. In particular, it should explicitly account for the project’s biggest risks — long lead times, permits and land, cost inflation over long horizons — rather than treating them as afterthoughts.