When does a group of projects become a major program?

When Does a Group of Projects Become a Major Program?

A collection becomes a programme when independent project success is no longer sufficient for the outcome. Shared interfaces, benefits, operating change and decisions mean one project can be on time while the combined investment still fails. The need for programme management comes from interdependence, not simply size or the number of workstreams.

Test five conditions: outputs must integrate to create value; benefits depend on coordinated adoption; projects compete for the same critical resources; risks propagate across boundaries; or sequencing decisions alter several business cases. If these are weak, a portfolio with common reporting may be enough. If they are strong, separate governance leaves system decisions without an owner.

A programme should own the target operating outcome, architecture, integrated roadmap, dependency model, benefit baseline and transition to use. Projects remain accountable for deliverables, but the programme can change scope and sequence across them to protect the whole. Funding needs contingency for shared risks rather than embedding buffers that cannot move between projects.

The 2026 Green Book defines a programme as a temporary organisation coordinating projects to deliver outcomes and benefits, while the 2025 Project Delivery Standard makes programme and portfolio governance roles mandatory. Both distinguish delivery products from the higher-level objectives those products serve.

Do not create a programme as an administrative layer. Define the decisions that only the programme can make, its authority over projects and the date it can dissolve after capabilities and benefits transfer to operations. A major programme exists when integrated value requires integrated choices�and when someone must be accountable for the spaces between projects.