Skip to content

Lesson 2 — Projects, Programmes, and Portfolios

At a glance

Learning objectives

By the end of this lesson you should be able to:

  1. Define programme and portfolio, and distinguish both from a project.
  2. Explain why organisations group work this way.
  3. Place a given piece of work correctly in the hierarchy.
  4. Explain what changes about your decisions when your project is one of many.

Prerequisites

Introduction

A single project rarely exists in isolation. It is usually one of several efforts competing for the same budget, the same specialists, and the same management attention.

This matters because it changes what "success" means. A project manager who optimises only for their own project can, quite rationally, make a decision that harms the organisation — and then be surprised by the reaction. This lesson explains the three levels at which work is organised, and what changes when you are one of many.

1. Three levels of organisation

Individual projects rarely stand alone. Organisations group related work so that they can coordinate it and decide where to invest. Three levels are usually distinguished:

Level Definition Question it answers Typical focus
Project A temporary effort producing a unique result How do we deliver this correctly? Delivery
Programme A group of related projects managed together for benefits that would not come from managing them separately How do these projects reinforce each other? Benefits
Portfolio A collection of projects and programmes selected and managed to meet strategic objectives Where should we invest at all? Strategy

The progression is from delivery, to benefits, to strategy.

flowchart TD
    accTitle: How portfolios, programmes and projects nest
    accDescr {
    A portfolio, described as strategic investment, contains Programme A, Programme B and one
    standalone project. Programme A contains Projects 1, 2 and 3; Programme B is not expanded.
    }
    P[Portfolio<br/>strategic investment] --> A[Programme A<br/>related projects + benefits]
    P --> B[Programme B]
    P --> C[Standalone project]
    A --> A1[Project 1]
    A --> A2[Project 2]
    A --> A3[Project 3]

2. Why the distinction matters

The levels differ in a way that changes the decisions you make, not just the vocabulary.

  • A project manager optimises for delivering this project's agreed outcome well.
  • A programme manager may deliberately delay or reduce one project so that the combined benefits across the programme arrive sooner. A decision that looks wrong at the project level can be right at the programme level.
  • A portfolio manager decides which work should be funded at all, and balances risk and return across everything the organisation is doing.

The same fact, seen from three levels

Project 2 is finished early.

  • At the project level, that is a success.
  • At the programme level, it may be a problem: Project 2's output is useless until Project 1 finishes, so finishing early simply ties up the people who could have helped Project 1.
  • At the portfolio level, it may prompt a question: if Project 2 finished early, was it over-resourced relative to the others?

3. Where a piece of work belongs

Classifying work is a skill worth practising, because it changes who you report to and what "success" means.

??? question "Classify: A university IT team runs five separate initiatives — a new student portal, a new timetabling system, a data warehouse, a security upgrade, and a website redesign — all funded from one annual budget." ??? note "Answer" The five initiatives are projects. Funded together from one budget and chosen against strategic goals, they form a portfolio. If, say, the student portal, timetabling system, and data warehouse all depend on the same new student-record system and are managed together for a combined student-experience benefit, those three could reasonably form a programme.

Classify: A single mobile app release that adds push notifications.
Answer

A project — temporary, with a unique result. It may be one of several projects delivering into the same product.

4. What changes when you are one of many

If your project is part of a programme or portfolio, several things shift:

  • Dependencies multiply. Other projects may depend on your output, and you on theirs.
  • Priorities can change for reasons outside your project. A change in strategy can stop your project, and that is not a failure of your management.
  • Shared resources create conflict. The same specialist may be needed by several projects at once.
  • Reporting has an audience beyond your sponsor. Portfolio reporting often standardises status so projects can be compared.

Practical consequence

When your project depends on another, record the dependency explicitly and agree who is responsible for monitoring it. Dependencies that are only in people's heads are missed at the worst possible moment.

Key terms

Term Meaning
Project A temporary effort delivering a unique result
Programme Related projects managed together for benefits unavailable from managing them separately
Portfolio A selected collection of projects and programmes managed to meet strategic objectives
Benefit An outcome of value to the organisation, distinct from a deliverable
Dependency A relationship in which one project's progress relies on another's output

Worked example

Task: classify a set of initiatives and find the decision that changes at each level. The organisation and its projects are illustrative.

Step 1 — List the work. A hospital's digital budget funds four initiatives: a new appointments system, a patient-records migration, a clinician dashboard, and a security upgrade.

Step 2 — Identify the projects. Each initiative is a project — temporary, with a unique result.

Step 3 — Identify the programme. The appointments system, records migration, and dashboard all depend on the same patient-record service and are managed together to improve outpatient care. Those three form a programme. The security upgrade is standalone work.

Step 4 — Identify the portfolio. Everything funded from the annual digital budget — the programme plus the standalone security work — is the portfolio.

Step 5 — Find the decision that changes. The dashboard project is running late. At the project level, the obvious response is to add effort. At the programme level, the better response may be to pause the dashboard and move its one available developer onto the records migration, because the migration must finish before the appointments system is usable. At the portfolio level, the question is different again: should so much have been committed to this programme while the security upgrade waits?

Step 6 — State the lesson. The same fact — "the dashboard is late" — produces three different right answers depending on the level at which you are deciding.

Common misconceptions

“Programme and portfolio are just bigger projects”

They answer different questions. A project delivers; a programme coordinates related projects for benefits; a portfolio decides where to invest at all. Managing them the same way loses the point of having them.

“Finishing early is always good news”

Not if the output is unusable until a dependency finishes. Early completion can tie up people who were needed elsewhere, and at programme level that is a problem, not a win.

“My project manager should protect my project”

A project manager should protect the project's agreed outcome, and be honest when the organisation's interests point elsewhere. Silently defending a doomed project is not loyalty; it is a failure to escalate.

Practical activity

Map your own portfolio. Choose an organisation you know — a university department, a workplace, or a set of modules in your own degree.

  1. List four to six pieces of active work.
  2. Classify each as project, programme, or portfolio level (and justify the borderline ones).
  3. Draw the dependencies between them as a Mermaid flowchart.
  4. Pick one and describe a decision that would look wrong at project level but right at programme level.

What "good" looks like: at least one genuine dependency between two pieces of work, and a justified example of a decision that differs by level. A diagram with no dependencies is either inaccurate or under-analysed.

Self-assessment

  1. What is the essential difference between a programme and a portfolio?
  2. Give an example where a decision that is good for one project is bad for the programme.

  3. Why should dependencies between projects be recorded rather than remembered?

  4. Apply it — university IT funding. A university IT division funds five initiatives from one annual budget: an admission portal, an LMS replacement, a data warehouse, a campus network upgrade, and a website redesign. Three of them — the portal, the LMS, and the warehouse — are placed under one manager because they share a student-data integration and the division wants a single identity platform across all three.

    Hint: A strong answer names all three levels and gives one decision that belongs to each.

Show answers
  1. A programme manages related projects together to gain benefits that managing them separately would not achieve. A portfolio is a selected collection of projects and programmes managed to meet strategic objectives and balance investment.
  2. Example: a project finishing early and releasing its specialists, when the programme needed those people on a delayed project to bring forward the programme's combined benefit.
  3. Because people change roles, memories fade, and silent dependencies are discovered only when they fail. A recorded dependency can be monitored and escalated.
  4. The five initiatives are projects. Funded together, chosen against the division's strategy, and balanced against each other from one budget, they form a portfolio. The three that were grouped for a shared integration and a shared identity platform form a programme — related projects managed together for a benefit none of them delivers alone. What changes for their manager: at project level you deliver to agreed scope and date; at programme level you sequence the three and share resources between them, and you may deliberately slow one to protect the combined benefit; the decision to fund or stop them at all belongs to the portfolio.

Summary

  • Project = delivery; programme = related projects managed for shared benefits; portfolio = strategic selection and balance across all work.
  • Each level answers a different question and optimises a different thing.
  • Being part of a programme or portfolio adds dependencies, shared resources, and priorities set outside your project.
  • Classifying work correctly tells you who to report to and what success means.

Further learning

Next

Continue to Lesson 3 — Project Life Cycles and Development Approaches, then take the Foundations quiz to check the whole module.