Skip to content
Technology transformation expertise firm · ARDIANE Group Innovate, secure, succeed

Glossary

PPM: definition of project portfolio management

Domain

Project management and PMO

In brief

PPM (Project Portfolio Management) is the discipline of choosing, prioritising and tracking all of an organisation's projects according to its strategy and its actual capacity. It answers a question that project management does not ask: are we doing the right projects?

Page contents

Definition of PPM

PPM is the acronym for Project Portfolio Management. The definition of PPM fits in one sentence: it is the discipline by which an organisation chooses the projects it undertakes, orders them and tracks them as a whole, according to its strategy and the resources it actually has.

A portfolio groups projects, programmes and sometimes recurring activities, brought together because they draw on the same resources: the same budget, the same teams, the same management attention. Its components do not need to be linked to one another. This is what distinguishes it from a programme, whose projects contribute to a common objective.

What project portfolio management is for

An organisation always has more project ideas than capacity to carry them out. Without a selection mechanism, everything starts, the same experts are called on everywhere and timescales stretch across all initiatives. PPM replaces this regulation by congestion with regulation by decision.

It answers three questions that nobody can address at the level of a single project:

  • Are we doing the right projects? Each project is measured against strategic objectives and expected value.
  • Can we do them? Demand is compared with capacity, skill by skill.
  • Are they keeping their promises? A project’s justification is re-examined along the way, not only at launch.

The stages of the portfolio cycle

The discipline is organised as a repeating cycle, most often in step with the budget and interim reviews.

  1. Inventory. Draw up the single list of everything that consumes change capacity, including projects launched without going through official channels.
  2. Assess. Describe each request in a common format: expected benefit, cost, risks, contribution to strategy, whether or not it is mandatory (regulatory, obsolescence).
  3. Prioritise and balance. Rank projects according to criteria known to all, then check the overall balance: short and long term, maintaining the existing estate and innovation, distribution between departments.
  4. Plan capacity. Check that scarce skills and the budget allow the selected projects to be run at the same time, and push back what does not fit.
  5. Track and re-arbitrate. Review the portfolio periodically, stop projects whose justification has disappeared and reallocate the freed resources.

The last stage is the most revealing. A portfolio in which no project is ever stopped or postponed is not managed: it is merely inventoried.

Project, programme, portfolio and PMO: not to be confused

Level Question addressed Lifespan
Project How do we deliver this result within the planned scope, timescale and budget? Temporary
Programme How do we coordinate related projects to obtain a shared benefit? Temporary, longer
Portfolio Which projects and programmes should we undertake, and in what order? Permanent

PPM is also distinct from the PMO, or project management office. The PMO is a structure, PPM a discipline. An enterprise PMO often runs portfolio management, but an organisation can practise PPM without a PMO, within a finance or strategy department for example.

Finally, by extension the acronym refers to portfolio management software. A PPM tool consolidates data, simulates scenarios and produces capacity views. It sets neither the priority criteria nor the trade-off rules: these choices are a matter of governance. In large-scale agile organisations, the same discipline takes other forms, such as the portfolio level of the SAFe framework.

A concrete example

An IT department receives some sixty project requests from the business each year. Until now, every request backed by a director was accepted. The architects and data experts, few in number, found themselves assigned to ten initiatives at once, and almost every project drifted.

Introducing portfolio management changes the process. Every request is described in a short sheet and scored against a shared grid. The forecast workload is compared with the capacity of the most sought-after profiles. A quarterly committee selects what can actually be carried out, postpones the rest and says so clearly to the requesters. The number of projects in progress falls, and those that remain finally have the people they need.

Signs of a genuinely managed portfolio

A few observations are enough to judge an organisation’s maturity: there is a single, up-to-date list of projects, the priority criteria are written down, capacity is examined before any launch, and projects are actually stopped or postponed during the year. The corresponding skills are described in several frameworks, including the portfolio management certification presented in our entry on PMI certifications.

To implement this discipline, see our page devoted to project portfolio management.

Insights

Further reading

All insights
The difference between a programme and a project, then the criteria that justify a programme

The difference between a programme and a project lies, in common usage, in what is accounted for: a project delivers a defined result, a programme brings together linked projects to obtain a benefit that none would produce alone. Management Square proposes here four criteria for deciding to set up a programme (common benefit, dependencies, shared resources, duration) and details the price of this choice.

Read the analysis
The project business case, measures to keep up after the budget is approved

A project business case is the document that justifies an investment by setting what the project costs against what it should bring in, by when and with what uncertainty. Management Square proposes here to treat it as four measures (full cost, benefits by type, timing, risks), each entrusted to a person who keeps it up to date, and to review it at each decision point.

Read the analysis
How to build an IT project roadmap and keep it up to date

An IT project roadmap links a project's objectives to dated milestones on a single page, shows what each milestone depends on and indicates the degree of certainty of each deadline. Management Square describes here the method for building it and then keeping it up to date: objectives, milestones, dependencies, capacity, levels of certainty, with what each step produces and who is accountable for it.

Read the analysis

FAQ

Frequently asked questions

Another question? Ask us

What does PPM stand for?

PPM stands for Project Portfolio Management. The term refers to the discipline used to select, prioritise and track all of an organisation's projects in light of its strategy, its budget and its available skills. By extension, it also refers to the category of software that supports this discipline.

What is the difference between PPM and project management?

Project management aims to run a given project well: scope, timescales, costs, quality. PPM sits one level above: it decides which projects deserve to be launched, in what order and with what resources, then checks that this choice remains relevant. A portfolio can be made up of very well managed projects and still be poorly chosen.

Do you need a PPM tool to manage a project portfolio?

No, not to begin with. A single list of projects, a shared assessment grid and a regular trade-off body are enough to establish the discipline. A tool becomes useful when the number of projects, capacity planning or financial consolidation exceed what a spreadsheet can reliably keep up to date.

Who is responsible for the project portfolio?

Portfolio decisions belong to management, meeting in a trade-off or investment committee. Preparing these decisions is generally entrusted to a portfolio manager or an enterprise PMO, which consolidates the data and prepares the cases without deciding in the executives' place.

A project to bring to completion?

A first conversation is enough to understand your challenge, identify the right people and tell you frankly what we can bring.