Project, Programme and Portfolio

The distinction

• Project — delivers a specific output within defined constraints. Success is measured by delivery: the right thing, on time, within budget, to standard.
• Programme — a group of related projects and activities managed together to deliver outcomes and benefits that could not be achieved by managing them separately. Success is measured by whether the change actually happened and the benefits appeared.
• Portfolio — the whole collection of projects and programmes an organisation is running, selected and balanced against strategy, capacity and risk appetite. Success is measured by whether the organisation invested in the right things.

The three answer different questions. A project asks "are we delivering this correctly?"; a programme asks "will this change achieve what we intended?"; a portfolio asks "are we doing the right things at all, and can we do them?"

When a programme is appropriate

Not every group of projects is a programme. A programme is justified where the projects share an outcome that none can achieve alone, where there are significant dependencies between them, where they compete for the same scarce resources, where their benefits are interdependent, or where the change requires coordinated organisational transformation.

Where projects are merely running at the same time in the same department, calling the collection a programme adds a management layer and no value. This is a common and expensive mistake: a programme office created to coordinate projects that have no genuine interdependence produces reporting, meetings and overhead while changing nothing.

The distinguishing feature of programmes

Projects deliver capability; programmes deliver change. A new system, a new process and a reorganised team are outputs; people working differently and a measurable improvement in performance are the outcome.

This is why programme management is substantially concerned with the things projects find inconvenient: business readiness, adoption, transition, sequencing of change so the organisation can absorb it, and the sustained effort after delivery that converts capability into benefit.

Programme characteristics

• Longer duration than its projects, often extending well beyond the last delivery.
• Less certain scope — the later projects are defined as the earlier ones reveal what is needed.
• Emergent — projects are added, changed and stopped as the programme learns.
• Outcome-focused, with success judged on benefits rather than on delivery.
• Tolerant of individual project variation, provided the overall outcome remains achievable.

That last point matters. A programme manager who manages the constituent projects as a set of delivery commitments has become a project manager with more projects, and has abandoned the part of the role that justifies its existence.