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

Project management and PMO

Project portfolio management (PPM): prioritise, arbitrate, manage capacity

A portfolio is not the list of your projects: it is the list of your choices. Our consultants help your leadership establish the criteria, the reading of capacity and the arbitration body that make it possible to start less and finish more.

Our principles

  • Prioritisation criteria owned by leadership
  • Capacity read through scarce skills
  • Trade-offs that include stopping projects
In brief

Project portfolio management (PPM) means choosing, ordering and regularly re-examining all of an organisation's projects in light of its strategy and its real capacity. Management Square consultants help a leadership team equip itself with the criteria, the data and the governance body that allow it to arbitrate between its projects, and not merely to track them.

Scope

How we contribute

  1. Portfolio inventory and qualification

    A census of all projects under way and pending, including those launched outside the usual channels, on a common record: objective, sponsor, cost, workload, dependencies, expected benefits.

  2. Prioritisation model

    Criteria, weightings and ranking rules built with your executive committee, then tested on the real portfolio before being adopted.

  3. Capacity management

    Comparing demand with available capacity, by critical skill and by period, to know what the organisation can really commit to.

  4. Arbitration body and cycle

    Mandate of the portfolio committee, calendar, format of submissions and rules for admitting, deferring and stopping projects.

  5. Value tracking

    Explicit benefit assumptions at launch, reread at every review and checked after delivery, with an identified business owner.

  6. Framing the PPM tool

    Requirements, selection and configuration of the portfolio management tool, once the process has been stabilised over a first complete cycle.

Page contents

Why project portfolio management disappoints

In many organisations, project portfolio management exists on paper. There is a list, a tool, sometimes a committee. But the list only grows, every project on it is a ‘priority’, and the committee rubber-stamps launches already decided elsewhere. The portfolio describes what is being done. It decides nothing.

The symptoms are familiar to all who endure them. Teams work on too many topics in parallel and spend their time switching context. Scarce skills (architects, data experts, security specialists) are booked by every project at once. Lead times lengthen everywhere without any one project being precisely at fault.

The cause is almost always the same: the organisation knows how to say yes, but has no mechanism for saying no, later or not like this. Launching a project takes a signature. Stopping one takes courage, facts and a body with the mandate to do so. This is the mechanism our consultants help you establish.

The four mechanisms of a portfolio that decides

A useful portfolio rests on four mechanisms that hold together. The definition of PPM in our glossary details the vocabulary. Here we focus on putting them into practice.

Prioritisation. It translates strategy into explicit criteria, known to those who propose projects. Several methods exist, and they do not suit the same situations.

Method Principle Suitable when Limitation
Weighted scoring grid Each project is scored on a few criteria (value, risk, urgency, effort) Projects are numerous and comparable Gives an illusory precision if the scores are not discussed
Strategic envelopes The budget is divided between categories before projects are ranked The portfolio mixes obligations, maintenance and development Requires a leadership decision on the split
Cost of delay Projects are ordered by what deferring them costs, relative to their duration Requests arrive as a flow and capacity is stable Assumes value and duration can be estimated
Forced ranking The committee orders projects one by one, with no ties The portfolio is small and the committee cohesive Hardly practicable for a large number of projects

Capacity. Prioritising without knowing your resources amounts to ranking wishes. Capacity is read at a coarse but reliable level: by critical skill and by period, not by person and by day. It is almost always a few scarce profiles that constrain the entire portfolio.

Arbitration. A body, a rhythm, submissions presented as options. The portfolio committee decides on admissions, deferrals and stops. It does not examine the progress of each project: that monitoring falls to the project office, or PMO, which prepares its submissions.

Value. Each project enters the portfolio with written benefit assumptions and a business owner. These assumptions are reread at every review. A project whose justification has disappeared along the way must be able to be stopped without anyone losing face.

Our approach: making the portfolio arbitrable before optimising it

Our consultants work within your teams; decisions remain yours. We do not start with a sophisticated scoring model. We start by making the portfolio readable, then we help hold a first real arbitration.

See. We take stock of all projects, including those that appear in no tool, and describe them on a common record. This step generally reveals duplicates, projects with no sponsor and initiatives everyone believed were finished.

Agree on the criteria. We help the members of the executive committee build the grid, testing it on the real portfolio. If the resulting ranking contradicts leadership’s intuition, it is the discussion that has value: it brings implicit criteria to light, which must then be written down.

Compare with capacity. We establish the workload requested and the capacity available for the skills that really constrain the portfolio. The result is a waterline: above it, the projects the organisation can carry out; below it, those that wait.

Decide. We prepare and facilitate with you a first committee that rules on this basis. The arrangement is then adjusted, and repeated at a fixed rhythm.

Tooling comes afterwards. When several projects in the portfolio are linked by a common objective, we recommend grouping them and running them using the methods of programme management.

Five traps we help you avoid

  • Taking the score for a decision. A grid informs a committee; it does not replace it. A ranking applied mechanically is circumvented as soon as the first poorly scored ‘strategic’ project comes along.
  • Planning capacity by the day. A named workload plan over many months is wrong as soon as it is published and costly to maintain. A coarse grain, kept up to date, serves decision-making better.
  • Forgetting ongoing activity. Maintenance, support and change requests consume the same capacity as projects. A portfolio that ignores them overestimates what it can commit to.
  • Leaving back doors open. If a project can be launched without going through the committee, the most influential requesters will take that route, and the official portfolio will no longer reflect reality.
  • Never rereading the benefits. A business case that no one reopens after launch encourages promising a lot. Rereading after delivery makes subsequent promises more measured.

How to measure the success of portfolio management

We agree with you on a few observable signs, tracked from one arbitration cycle to the next.

  • The share of projects under way that have gone through the decision channel.
  • The number of projects run in parallel, relative to the capacity of critical skills.
  • The existence of explicit decisions to defer or stop, and their actual application.
  • The stability of priorities between two reviews: priorities that change at every committee signal poorly framed criteria.
  • The share of delivered projects whose benefits have been reread with the business owner.
  • The time between a project request and the answer given to it.

None of these indicators measures the committee’s activity. All of them measure the same thing: the organisation’s ability to concentrate its resources on a number of projects it can finish.

Typical work

What our consultants contribute to

Portfolio map

A consolidated view of projects by strategic axis, by department and by level of commitment, with the major dependencies.

Prioritisation grid

Criteria, scoring scales and rules of use, together with the ranking obtained on the current portfolio.

Capacity plan

Workload requested and capacity available by critical skill, with saturation points and smoothing scenarios.

Portfolio committee charter

Membership, powers, frequency, format of arbitration submissions and the path by which decisions are applied.

Insights

Further reading

All insights
Drawing up an application modernisation roadmap for an entire estate

An application modernisation roadmap gives each application in an estate a treatment route, a rank and a decision point, then arranges these lines according to dependencies and available capacity. Management Square proposes a six-step method here for drawing it up, from the survey of the estate to the review rule, and indicates the tangible result of each step.

Read the analysis
In programme governance, who decides, at what level and on what information?

Programme governance refers to the rules that set who decides what in a programme, at what level, on what information and within what timescale. Management Square proposes here an allocation of decisions, following the questions of an executive committee about to fund a programme: inventory of decisions, delegation thresholds, information for the board, disputes between projects, closure.

Read the analysis
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

Management Square in figures

300+
projects completed
43+
clients supported
Since2015
serving our clients
  • Allianz
  • Euler Hermes
  • Groupe BPCE
  • ODDO BHF
  • Candriam
  • Ledger
  • Saur
  • Veolia
  • Voltalia
  • emeis
  • Bonpoint
  • Legal Suite

FAQ

Frequently asked questions

Another question? Ask us

What is project portfolio management?

Project portfolio management, or PPM, is the discipline of selecting and prioritising an organisation's projects, comparing them with available capacity and re-examining these choices at regular intervals. It answers the question 'are we doing the right projects?', whereas project management answers the question 'are we doing this project right?'.

What is the difference between a PMO and portfolio management?

A PMO is a structure; portfolio management is a discipline. A PMO may limit itself to harmonising practices and consolidating progress, without taking part in choosing projects. Portfolio management requires a body with the power to launch, defer and stop projects, which the enterprise PMO most often prepares and facilitates.

How do you prioritise projects of very different kinds?

By avoiding ranking them all on a single scale. A proven practice is first to divide the budget and capacity between a few envelopes (regulatory obligations, run and maintenance, development, innovation), then to prioritise projects within each envelope using suitable criteria. A regulatory project and an experiment cannot be compared using the same grid.

Do you need PPM software to manage a portfolio?

Not to begin with. A first arbitration cycle can be held with a common project record and a well-built spreadsheet. The tool becomes useful once the process is stable, the volume of projects justifies it and the workload data is reliable. Chosen too early, it freezes a process that no one has yet tested.

Does portfolio management apply to agile organisations?

Yes, with different objects. In an organisation structured around products, the portfolio arbitrates budgets allocated to value streams and major initiatives rather than projects with an end date. The mechanisms remain the same: explicit priorities, known capacity and a regular review of choices.

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.