Project portfolio management, usually shortened to PPM, is the centralized practice of selecting, prioritizing, funding, and continuously reviewing an organization's collection of projects and programs so that limited money and people are spent on the work that advances strategy. PMI defines a portfolio as "a collection of projects, programs, subsidiary portfolios, and operations managed as a group to achieve strategic objectives." The components need not be related to each other. What makes them a portfolio is that they compete for the same resources and are judged against the same strategy.
The distinction that gives PPM its reason to exist is a question of authority. Project management is accountable for doing the project right. Portfolio management is accountable for doing the right projects, which necessarily includes the authority to stop one. An organization that runs excellent project management and no portfolio management delivers a great many things nobody needed, on time and within budget.
Key takeaways
- PPM stands for project portfolio management. Its object is the set of all projects, not any single project.
- It does five things: intake, prioritization, resource allocation, continuous review, and benefits tracking.
- The defining power of a portfolio function is the power to stop or defer work. Without it, PPM is reporting.
- The constraint that makes prioritization real is capacity, not budget. Most portfolios are approved beyond the number of people available to execute them.
- PPM is not a tool. Software helps once the decision rights exist and is expensive theater before that.
- The most common failure is a portfolio that is reviewed annually. Strategy changes faster than a budget cycle.
What does PPM stand for in project management?
PPM stands for project portfolio management. You will also see the term written as project and portfolio management, which means the same thing and is the phrasing several enterprise vendors prefer. Outside project management, PPM more commonly means parts per million, so context matters when searching.
A related term worth separating early: a project manager portfolio is a personal collection of work a project manager shows to a prospective employer. That is a career artifact and has nothing to do with the discipline described here, despite the near-identical phrasing.
What project portfolio management actually does
Strip away the vocabulary and PPM is five recurring activities. Each is a decision point where an organization can be honest or can avoid a conversation.
| Activity | The question | The failure when it is skipped |
|---|---|---|
| Intake | What is being proposed, and in a comparable format? | Projects begin because someone senior asked, and never enter the portfolio at all. |
| Prioritization | Which of these are worth more than the others? | Everything is priority one, so sequencing is decided by whoever escalates hardest. |
| Resource allocation | Do we have the people, and when? | The portfolio is approved against budget and executed against capacity, which is a different and smaller number. |
| Continuous review | Is this still worth finishing? | Projects are killed by exhaustion rather than by decision, months after everyone knew. |
| Benefits tracking | Did the investment return what was promised? | Nobody learns which business cases were fiction, so the next round is written the same way. |
The five run as a loop rather than a sequence, and the loop is the part that gets skipped. Each activity has a page of its own here: the project intake process, how to prioritize a project portfolio, resource and capacity planning, the portfolio review meeting, and benefits realization management. The full seven-step lifecycle, in order, is set out in the project portfolio management process.
Portfolio management, program management, project management
Three tiers, three different objects of accountability. A project delivers an output. A program coordinates related projects to deliver an outcome they cannot deliver separately. A portfolio holds everything and decides what gets to exist.
| Project | Program | Portfolio | |
|---|---|---|---|
| Object | One defined output | Related projects with a shared outcome | All investments competing for the same resources |
| Core question | Are we delivering this well? | Are these pieces adding up? | Should we be doing this at all? |
| Success measure | Scope, schedule, cost, quality | The outcome and its benefits | Strategic alignment and portfolio value |
| Time horizon | Fixed. It ends. | Multi-year, ends when the outcome lands | Continuous. It never ends. |
| Defining authority | Manage the plan | Manage the interdependencies | Fund, defer, or stop |
The tiers are covered in depth on their own pages: project portfolio management vs project management takes the portfolio-to-project comparison, and program management vs project management takes the middle tier.
An example of project portfolio management
Illustrative, with round numbers chosen for clarity rather than drawn from a specific company. A mid-sized insurer has an annual change budget of $20M and 120 people who can actually staff delivery. Business units submit 34 proposals asking for $31M.
The naive response is to fund the $20M of proposals with the highest stated return. That is the response that fails, and it fails for a reason worth understanding: the returns were written by the people asking for the money, they use inconsistent assumptions, and the $20M of work selected this way will require roughly 180 people. The portfolio is approved against the budget and executed against the capacity, and by March everything is late.
What a functioning portfolio function does instead is force the proposals into a comparable shape, score them on criteria agreed before anyone saw the list, and then apply the binding constraint. In this case the constraint is not the $20M. It is the 120 people, and more precisely it is the eleven integration engineers that nine of the 34 proposals all quietly assume they can have. Prioritization that ignores that specific bottleneck will produce a beautifully ranked list that cannot be executed. The mechanics of scoring the list are in project scoring models and project prioritization criteria.
The output is a funded set of perhaps 19 projects, an explicit deferred list, and, if the organization is being honest, two or three in-flight projects stopped to release the engineers the new work needs. That last act is the one that distinguishes portfolio management from portfolio reporting. Everything up to it is analysis. Only the stop decision changes where the money goes.
What are the benefits of project portfolio management?
The benefits are usually stated as a list of abstractions. It is more useful to state them as things that stop happening.
- Fewer zombie projects. Continuous review means work that has lost its rationale is stopped by decision rather than quietly starved for two years.
- Sequencing that reflects capacity. When allocation is done against people rather than budget, the start dates are ones the organization can actually meet.
- Comparable business cases. A common intake format means two proposals can be compared without an argument about whose spreadsheet is more optimistic. See the project business case.
- Visible tradeoffs. Saying yes to one thing becomes visibly a no to another, in the same meeting, which changes how people ask.
- Feedback into the next cycle. Tracking whether promised benefits arrived tells you whose forecasts to trust, which is the only mechanism that ever improves a business case.
- Dependency exposure before it bites. Cross-project dependencies are visible at portfolio level and nowhere else. Each project manager sees only their own side of one. See project dependency management.
Who is responsible for project portfolio management?
In most organizations the practice sits with a PMO or an enterprise PMO, and the decisions sit with a portfolio board or investment committee of executives who control budget and people. The distinction matters. The PMO runs the process, prepares the analysis, and enforces the intake standard. It does not decide. When a PMO believes it decides, it acquires all the resentment of a gatekeeper and none of the authority, which is the shortest path to being disbanded.
The individual accountable for running the discipline day to day is usually a project portfolio manager. Where the decision rights sit, what thresholds trigger which forum, and who is permitted to stop a project are questions of project portfolio governance.
Do you need PPM software?
Not to start, and buying it early is a reliable way to entrench a broken process in an expensive system. What PPM software does well is aggregate data an organization is already collecting: capacity against demand, spend against forecast, benefits against baseline. What it cannot do is create the decision rights that make a portfolio review meaningful. Organizations that install a tool before agreeing who can stop a project end up with a very well-instrumented view of a portfolio nobody is managing.
A spreadsheet is enough for a portfolio of perhaps 30 projects, and honest scoring in a spreadsheet beats sophisticated scoring in a system nobody trusts. The point at which tooling starts paying for itself is roughly where resource contention across projects becomes impossible to see by hand. The vendor landscape and how to think about it is covered in project portfolio management software and PPM tools, and what to measure once you have it is in PPM KPIs and metrics.
Frequently asked questions
What is project portfolio management?
Project portfolio management is the centralized selection, prioritization, funding and continuous review of an organization's projects and programs, so that limited money and people go to the work that best advances strategy. Its distinguishing authority is the power to defer or stop a project, not merely to report on one.
What is the difference between project management and portfolio management?
Project management is accountable for delivering one defined output well, within scope, schedule and cost. Portfolio management is accountable for deciding which projects should exist at all and which should stop. One optimizes execution, the other optimizes selection. An organization can be excellent at the first and still spend its budget on the wrong work.
What does PPM stand for?
In project management, PPM stands for project portfolio management, sometimes written as project and portfolio management. The abbreviation is also widely used for parts per million in chemistry and engineering, which is why searches for "PPM meaning" return both.
What are the five stages of project portfolio management?
Intake, prioritization, resource allocation, continuous review, and benefits tracking. They run as a loop rather than a straight line, and the loop is what most organizations omit: they perform intake and prioritization once a year and never revisit whether an approved project still deserves its funding.
Is project portfolio management the same as PMO?
No. PPM is the discipline. A PMO is an organizational unit that commonly runs it. A PMO can exist without doing portfolio management, and many do, restricting themselves to methods, templates and reporting. Portfolio management can also be run by a strategy or finance function with no PMO involved.
What is an example of a project portfolio?
An insurer's change portfolio might hold a claims system replacement, a regulatory reporting program, three pricing analytics projects, and a branch consolidation. They share no scope and no deliverables. They are one portfolio because they compete for the same $20M and the same 120 delivery staff, and because they are judged against the same strategy.
Who is responsible for project portfolio management?
A PMO or enterprise PMO typically runs the process, while a portfolio board or investment committee of budget-holding executives makes the funding and stop decisions. Day-to-day the discipline is usually led by a project portfolio manager. Separating the process owner from the decision maker is what keeps a PMO from being resented as a gatekeeper.