What is project portfolio governance? It is the set of rules and routines a company uses to decide which programmes to fund, check how they are going, and step in when they drift. In practice, it comes down to one question a sponsor asks every month: across everything we are paying for, where do I need to act?
Most sponsors cannot answer that quickly. They get twelve status reports in twelve formats, budgets in four currencies, and a RAG colour that means something different on every programme. Good portfolio governance fixes the view before it fixes anything else. This article sets out what the sponsor needs to see, and why.
What is project portfolio management, and what does a portfolio manager do?
A project delivers a defined piece of work. A programme groups related projects so they deliver one business outcome, such as a new ERP. A portfolio is everything the organisation is investing in, often several programmes plus standalone projects, managed as a whole.
Project portfolio management (PPM) is the practice of choosing, balancing and overseeing that whole set. Governance is the decision-making part of it: who approves what, on what evidence, and how often.
So what does a project portfolio manager do? In most PMOs the job looks like this:
- Sets the reporting standard every programme must follow
- Keeps the portfolio view current and honest
- Spots problems that cross programmes, such as two projects needing the same people
- Prepares the decisions sponsors must make, with options and costs
- Tracks whether funded programmes still justify their budget
The one-page view a sponsor needs
A sponsor should be able to see the whole portfolio on one page in under two minutes. If it takes longer, the page is a report, not a governance tool. Here is what I put on it.
A sponsor's one-page portfolio view
- Total budget for the portfolio, in one currency
- Actual spend to date and forecast at completion
- Number of programmes by RAG status
- Schedule position: which programmes are behind, and by how much
- Open high and critical risks across the portfolio
- Decisions waiting for the sponsor
- A table of every programme that can be sorted by any of the above
Notice what is missing: long narrative. Narrative belongs one click down, on the programme's own status report. For how to write that report well, see how to report project status to executives.
Consistent RAG: one meaning of red across every programme
RAG stands for red, amber, green. It only works at portfolio level if every programme uses the same rules. If one programme manager calls a two-week slip amber and another calls a two-month slip amber, the sponsor's page is lying, even though nobody meant it to.
RAG that hides
- Each programme sets its own thresholds
- Green until the week before a missed milestone
- Colour chosen by feel, with no figures behind it
- Amber used as a safe place to sit for months
RAG that tells
- One written rule for the whole portfolio
- Thresholds tied to schedule, cost and risk figures
- Every colour backed by the numbers beside it
- Amber always comes with a recovery date
Write the rule down and publish it. For example: amber when the forecast overruns budget by more than five percent or a key milestone slips by more than two weeks; red when the overrun or slip needs a sponsor decision. Your thresholds may differ. What matters is that everyone uses the same ones.
One budget total, even across currencies
Global companies run programmes in different currencies. A rollout in Germany is budgeted in euros, the one in India in rupees, the one in the US in dollars. Add them up without converting and the total is meaningless. Convert them with whatever rate each finance team used, and the total is still unreliable.
How to get one honest budget total
- Pick one reporting currency
Usually the group's reporting currency, agreed with the CFO.
- Agree the rates
Finance sets one rate per currency, with the date it applies from.
- Keep programmes in their own currency
Each team budgets and records cost in the currency it really spends.
- Convert at portfolio level
Convert every programme with the same rates, then add them up.
- Show the rate date
Print the as-of date beside the total so nobody mistakes it for a live market figure.
This matters most for the forecast. A programme that is on budget in local currency can look like an overrun in group currency simply because rates moved. Showing the rate date lets the sponsor tell the two apart. For the real causes of overruns, see why projects go over budget.
Drill-downs: from the total to the line that explains it
A one-page view raises questions. Why is this programme red? Where did the overrun come from? Which risks are open? The sponsor should be able to answer those by clicking, not by emailing the PMO and waiting three days.
Good drill-downs follow the same areas as the summary page: budget, schedule, risks and issues, resources, quality and status. Each one opens from the portfolio level to the programme level, then to the individual line. The figures at every level must add up to the level above. If they do not, trust in the whole view goes quickly, and people go back to their own spreadsheets.
How ProjectCAPEX gives sponsors this view
The ProjectCAPEX portfolio overview shows one budget total in your reporting currency, using the rates your company sets, with the as-of date shown. It shows programmes by RAG, and a tile for each area (budget, schedule, RAID, quality, resources and status) that opens its own drill-down. Every programme sits in a sortable table below. An executive sponsor lands on a Home page that shows their approvals under a portfolio status strip, so the decisions waiting for them sit right next to the numbers they need to make them. Try the demo or start your workspace.