keymodels
Benefits Breakdown Structure
How can benefits breakdown structure support strategic choice or positioning?
Contents
While a Program Work Breakdown Structure is a recognized best practice in program management, a Benefits Breakdown Structure also is useful. Thiry (2004).
A Benefits Breakdown Structure (BBS) complements the familiar Program Work Breakdown Structure by showing how delivery contributes to value. Michel Thiry described the functional diagramming method in 2004 and later applied it to programmes. The structure traces the logic through which projects and non-project work create capabilities, benefits and strategic outcomes that realise the programme vision.
When to use it
- To understand and communicate the benefits logic of a programme through a reusable structure.
- To align teams around how components, capabilities, benefits and strategic objectives connect.
- To turn benefits identified in the business case into owned, measurable benefit packages.
Context
This working artefact supports programme benefits management. Tailor its terminology, ownership and level of decomposition to the organisation’s governance model, stakeholders and delivery life cycle.
What it is
Continue your preview
Read more of Benefits Breakdown Structure.
Create a free account to continue this advanced article preview. Complete access is available with Pro or an eligible outcome pack, so you can see the value before deciding to upgrade.