Project vs Program vs Portfolio Management: Key Differences

Project, programme and portfolio: the short answer

A project is a temporary effort to create a unique product, service or result. A programme is a group of related projects and activities managed together to achieve benefits that none could deliver alone. A portfolio is the full collection of projects, programmes and other work an organisation selects, prioritises and funds to meet its strategic objectives.

Think of it as three questions. Project management asks "are we doing this piece of work right?" Programme management asks "are these related pieces of work adding up to the change we need?" Portfolio management asks "are we doing the right work at all?"

Official definitions

The Project Management Institute (PMI) publishes a separate standard for each level: the PMBOK Guide for projects, The Standard for Program Management (fifth edition, 2024) and The Standard for Portfolio Management. Its definitions, summarised:

In the UK and many Commonwealth countries the same three levels are often called P3M (portfolio, programme and project management), and the programme level is covered by the MSP (Managing Successful Programmes) method alongside PRINCE2 for projects.

Key differences at a glance

What is project management?

Project management is the application of knowledge, skills, tools and techniques to project activities to meet project requirements. A project manager plans the work, leads the team, manages risks, issues and changes, keeps stakeholders informed and hands over the finished result. Success is usually judged on delivering the agreed scope within time, cost and quality limits.

Projects can stand alone. A small company refurbishing its reception area has a project, not a programme, and probably no formal portfolio. Projects can also sit inside a programme, or directly inside a portfolio when they are not related to other work.

For the basics, see what is a project and what is project management.

What is programme management?

Programme management is the coordinated management of a group of related projects and activities to achieve benefits and outcomes that the projects could not achieve separately. A programme exists because the projects depend on each other: they share resources, deliver parts of the same change, or only create value when they come together.

Why group projects into a programme?

• Dependencies: one project's output is another's input, so schedules and changes need coordinating.
• Shared resources: the same specialists, budget or suppliers are needed across projects.
• Combined benefits: the benefit only appears when several outputs are in use together, such as a new system plus new processes plus trained staff.
• Consistent governance: one sponsor and one board can direct related work instead of several competing ones.
• Managing change in the business: programmes typically include business change and transition activities, not just project deliverables.

Benefits management

Benefits are what set programmes apart. A programme team identifies the benefits it expects (for example, faster processing times or higher customer retention), maps which project outputs enable them, assigns owners in the business, and tracks them during and after delivery. Because many benefits appear only once the new ways of working are embedded, programmes often continue after their last project has closed.

The programme life cycle

PMI's Standard for Program Management describes a life cycle of programme definition, programme delivery (where component projects are started, delivered and closed) and programme closure. In practice that means: define the vision and benefits, design the set of projects, deliver them in tranches or waves, embed the changes and confirm the benefits, then close. The fifth edition (2024) also sets out eight principles and adds a Collaboration performance domain.

What a programme manager does

A programme manager rarely manages tasks directly. They coordinate project managers, resolve conflicts over resources and priorities, manage dependencies and risks that cross project boundaries, keep the roadmap aligned with the benefits, and report to the programme sponsor or board.

What is portfolio management?

Portfolio management, often called project portfolio management (PPM), is the centralised selection, prioritisation and oversight of an organisation's projects, programmes and related operational work to achieve its strategic objectives. Where programme management asks how to deliver a set of related changes, portfolio management asks which changes the organisation should invest in at all, and in what order.

Two points cause the most confusion. First, the work in a portfolio does not need to be related: a portfolio may contain an IT upgrade, a new product and a training initiative. Second, PMI's definition includes operations, because ongoing work competes for the same money and people as change work.

The portfolio management process

1. Identify candidate initiatives from strategy, business units and demand.
2. Evaluate each one using a business case: costs, benefits, risks and strategic fit. Measures such as return on investment help compare options.
3. Prioritise and select using agreed criteria, and decide what to start, defer or reject.
4. Balance the portfolio across risk, time horizon, business area and available capacity. See capacity planning.
5. Authorise the chosen work and allocate funding and resources.
6. Monitor and review performance regularly, and rebalance: accelerate, change, pause or stop work as conditions change.

Common prioritisation criteria

• Strategic alignment: how directly the work supports stated objectives or OKRs.
• Value: financial return, cost savings, revenue or customer impact.
• Risk and urgency: regulatory deadlines, safety, or the cost of delay.
• Feasibility: whether the organisation has the skills, capacity and budget now.
• Dependencies: whether other work relies on it.

Portfolio decisions are usually made by a portfolio board or investment committee, supported by a portfolio manager and often a PMO. Tools such as our OKR template and business case template help connect strategy to the work being proposed.

How the three levels work together

The three levels form a hierarchy of decisions, not just of size. Strategy shapes the portfolio, the portfolio authorises programmes and projects, and programmes coordinate their component projects.

When this works well, a project manager knows why their project matters and what to escalate, a programme manager can move resources between projects, and the portfolio board can stop work that no longer earns its place. Good project governance defines who makes each of these decisions.

Worked example: a hospital

• Portfolio: all of the hospital's change initiatives, managed by a portfolio board that balances clinical, digital, estates and workforce investment against its strategy and budget.
• Programme: a digital health programme within that portfolio, aiming to cut outpatient waiting times and improve patient experience. Its programme manager coordinates the projects below and tracks benefits such as appointment waiting times.
• Projects: a patient app, an upgrade to electronic patient records, integration between the two, and staff training. Each has its own project manager, plan and deliverables.
• Standalone project in the same portfolio: a car park resurfacing project. It is unrelated to the programme, so it sits directly in the portfolio.

If the app is delayed, the programme manager decides how that affects the records upgrade and training and whether benefits will slip. If a new regulatory requirement appears, the portfolio board may pause the car park project to free up budget.

More examples

Roles and responsibilities at each level

On smaller programmes some of these roles are combined; on the largest each may be a full-time team. For the project level in detail, see project manager roles and responsibilities.

Project, programme or portfolio: which do you need?

Start from the work, not the label. These questions help you decide how to organise it:

1. Is there one clear output that a single team and plan can deliver? Run it as a project.
2. Do several projects depend on each other, share scarce resources or only create value together? Group them into a programme.
3. Does the organisation run more projects than it has people or money for, or struggle to say which work matters most? Introduce portfolio management.

Signs you need a programme

• Project managers keep negotiating with each other over the same people or dates.
• Nobody owns the overall outcome, only individual deliverables.
• Benefits depend on business change as well as new systems or products.

Signs you need portfolio management

• Too many projects start and too few finish.
• Teams are spread across many projects and everything is "top priority".
• Leaders cannot see all current work, its cost or its status in one place.
• Projects carry on after their business case has stopped making sense.

Portfolio management does not have to be heavy. A single prioritised list of all work, reviewed monthly by the people who control budgets, is a good start. If you personally juggle several projects, see managing multiple projects.

Programme and portfolio management in Agile organisations

Agile organisations use the same three levels with different mechanics. Instead of approving fixed-scope projects one by one, they often fund long-lived teams or value streams and adjust priorities in short cycles.

• Lean portfolio management funds value streams rather than individual projects and reviews priorities regularly. See Agile portfolio management.
• Agile Release Trains in the Scaled Agile Framework (SAFe) play a role similar to a programme: several teams plan and deliver together. See Agile Release Train.
• PI planning works like a programme-level planning event, aligning teams on objectives for the next increment.
• Roadmaps replace detailed long-range plans at portfolio and programme level. See project roadmap.

The questions stay the same: are we investing in the right work, are related pieces of work coming together, and is each team delivering well?

Careers and certifications

A common career path runs from project coordinator to project manager, then senior project manager, programme manager and portfolio manager or head of a PMO. The skills shift from planning and delivery towards stakeholder influence, benefits, finance and strategy.

PgMP and PfMP require several years of programme or portfolio experience on top of project experience, so most people earn them later in their career. Check the current eligibility rules on pmi.org before you apply.

Tools for managing projects, programmes and portfolios

Managing a single project needs tasks, a timeline and collaboration. Programme and portfolio work adds requirements: roll-up dashboards across many projects, cross-project dependencies, resource and capacity views, intake and approval workflows, and reporting on budgets and benefits.

Many work management platforms now cover all three levels to some degree. Our #1-ranked tool, Wrike, is a good fit for organisations that need cross-project dashboards, resource planning and custom request workflows.

Common mistakes

• Calling a big project a programme. The label adds governance overhead without adding coordination value if the work has one output.
• Treating the portfolio as a list. A portfolio needs active decisions: selecting, balancing and stopping work, not just recording it.
• Measuring programmes like projects. A programme that is on time and on budget but delivers no benefits has failed.
• Starting everything at once. Approving more work than the organisation has capacity for slows everything down. See resource allocation.
• Ignoring operations. Business-as-usual work uses the same people as change work; leaving it out of portfolio decisions gives a false picture of capacity.
• No link to strategy. If nobody can explain how a project supports an objective, question whether it belongs in the portfolio.

Free templates for this topic

Browse all templates

Frequently asked questions