Certified Associate in Project Management (CAPM)
Project vs program vs portfolio: the differences for CAPM
A project is a temporary piece of work that delivers one or more products or outputs. A program coordinates a set of related projects and activities to deliver outcomes and benefits. A portfolio is part or all of an organization's investment, made up of programs, projects and other work, needed to meet its objectives.
The three definitions
The UK Green Book uses the government's project delivery definitions. A project is a unique, temporary management environment, undertaken in stages, created to deliver one or more business products or outcomes. It can stand alone in a portfolio or sit inside a program.
A program is a unique, temporary, flexible organization created to coordinate, direct and oversee a set of projects or related activities, to deliver outcomes and benefits tied to a set of objectives. It can run in one or more tranches.
A portfolio comprises part or all of an organization's investment required to achieve its objectives. It contains other portfolios, programs, projects and related work.
Outputs, outcomes and length
The FCDO Programme Operating Framework puts the split simply. Projects are discrete, time-bound interventions usually designed to produce certain outputs. A program is a thematic set of projects and activities designed to bring about outcomes that support higher-level strategic objectives.
The Green Book says shorter-term objectives are delivered through projects. Longer-term and more complex objectives are delivered through programs, which oversee a series of underlying projects.
Not everything in a program is a project. The FCDO framework says a program budget can also pay for non-project activities, such as the cost of staff funded from the program, monitoring, research or audits.
How objectives flow down
Changes set at the policy level are put into effect by one or more portfolios. Each portfolio sets objectives from those changes and consists of the programs and projects needed to meet them. Programs and projects then take their objectives from the level above. The Green Book calls this alignment the golden thread.
So a project's appraisal does not have to justify its program. In the Green Book's railway example, the signalling project is judged on the best way to install signals, not on the transport needs of the town, which the railway program has already established.
Where the exam catches people
- Believing a program is just a large project: a program coordinates several projects and activities to deliver outcomes and benefits.
- Believing a portfolio is a group of related projects only: it is part or all of an organization's investment and can hold programs, projects, other portfolios and other work.
- Believing everything a program pays for must be a project: a program budget can fund non-project activities such as staff costs and audits.
- Believing each project must justify the whole program: a project's objectives are set by the program or portfolio above it.