Project Portfolio Management (PPM): Process and Best Practices

Project portfolio management (PPM) is how organizations decide which projects to fund, which to pause, and which to kill before they drain the budget. If your company runs more than a handful of projects at once, the real competitive advantage isn't execution speed on any single project. It's choosing the right mix to begin with.

What is project portfolio management (PPM)?

Project portfolio management (PPM) is the centralized process of selecting, prioritizing, and governing a collection of projects and programs so that the overall mix delivers the greatest strategic value given available resources, budget, and risk tolerance.

Where individual project management asks "are we running this project well?", PPM asks "are we running the right projects?" It treats the project portfolio the same way a fund manager treats an investment portfolio: the goal isn't to maximize returns on one position, it's to balance the whole book so the organization can hit its targets while absorbing the inevitable losses.

PPM sits at the intersection of strategy and execution. The project management office (PMO) typically owns or supports PPM, though in some organizations a dedicated Portfolio Management function reports directly to the C-suite.

Key Facts

• PMI's 2020 Pulse of the Profession report found that organizations waste an average of $135 million for every $1 billion invested in projects, much of it tied to misaligned project selection rather than poor execution.
• Gartner (2023) found that only 56% of strategic initiatives fully meet their business objectives, with portfolio misalignment cited as a leading cause.
• According to PMI's PMBOK Guide (7th edition), portfolio management is a distinct discipline from program and project management, with its own governance framework and performance domains.

Project management vs portfolio management

People often conflate these, so let's be direct about the difference.

Program vs. project management sits in between: a program groups related projects to realize benefits that no single project delivers alone. PPM sits above programs and projects both, treating them all as investment options.

The project portfolio management process

PPM isn't a one-time exercise. It runs on a cycle, typically quarterly or in sync with the annual planning calendar. Here's how each step works in practice.

Step 1: Build the project inventory

You can't manage what you can't see. The first step is creating a complete register of every active, proposed, and paused project across the organization. This sounds obvious, but most companies are shocked to discover how many unofficial "shadow" projects are running without budget approval.

Pull from every source: PMO systems, finance requests, IT roadmaps, departmental plans. Capture the sponsor, estimated cost, strategic goal it supports, current status, and resource demand. This inventory becomes your portfolio baseline.

Step 2: Score and prioritize each project

Once you have the full list, each project needs a score that reflects its value to the organization. A weighted scoring model works best here (see the next section for detail). Typical scoring dimensions include strategic alignment, expected financial return, risk level, urgency, and dependencies.

The score doesn't replace judgment, but it creates a defensible, repeatable basis for prioritization conversations. Without a scoring model, portfolio decisions default to whoever shouts loudest in the budget meeting.

Step 3: Assess resource capacity

A high-scoring project is worthless if no one has the bandwidth to run it. At this step you map demand against supply: how many skilled people, budget dollars, and tool licenses does the portfolio require, versus what's actually available?

This is where capacity planning and resource allocation data become critical inputs. If your engineers are already at 110% utilization, adding three more "high priority" projects doesn't accelerate strategy. It guarantees all three projects will deliver late.

Step 4: Select and authorize the portfolio

With scores and capacity data in hand, the portfolio board (or executive sponsor group) selects which projects move forward. This step involves three decisions: which to fully fund, which to phase or delay, and which to stop.

Stopping a project already underway is hard emotionally, but it's one of PPM's highest-value actions. Sunk cost is irrelevant. The only question is whether future investment in a project returns more value than the next best alternative in the portfolio.

Each selected project should have a signed project charter and a clear owner before it enters active execution.

Step 5: Monitor active projects

PPM doesn't end at selection. The portfolio team tracks active projects against their promised benefits, not just schedule and budget. A project can be on time and on budget but delivering something that no longer aligns with the current strategy.

Standard monitoring checkpoints include: monthly health reports from project managers, quarterly portfolio reviews, and trigger-based reviews whenever a major risk materializes. A risk register at the portfolio level captures shared risks that cut across multiple projects (such as a key vendor dependency or a regulatory change).

Step 6: Rebalance as strategy evolves

Markets shift. Priorities change. A project that scored highly six months ago may no longer justify its resource footprint. Good PPM builds in explicit rebalancing cycles where the portfolio is re-scored against the current strategy and adjusted accordingly.

This is the step most organizations skip. They select projects annually but never revisit the decision mid-year. By the time the next planning cycle arrives, the portfolio has drifted and half the projects are delivering against an obsolete strategy.

Project prioritization and scoring models

Two tools dominate PPM prioritization in practice.

Weighted scoring model

Assign weights to each strategic dimension that matters to the organization, then score each project against those dimensions. The result is a single number you can rank-sort.

Here's a simple example with five dimensions:

Project A edges ahead despite a lower expected NPV because it aligns better with strategy and is more feasible to resource. This is the kind of nuance a pure financial ranking would miss.

Cost of delay

Cost of delay (CD) quantifies what the organization loses for every week or month a project is postponed. It makes the "sequence" decision concrete: if two projects compete for the same team, which one should go first?

The customer portal has a cost of delay ratio more than five times higher. It should be sequenced first even if the reporting tool is smaller and faster. This isn't intuitive without the numbers.

Project portfolio management examples

Technology company: A SaaS business maintains a portfolio of 40 active projects split across three categories: product development (60% of budget), infrastructure (25%), and internal process improvements (15%). Each quarter the CTO and CPO review the product portfolio against monthly active user data. Projects where user adoption metrics are flat get a six-week window to show improvement before resources are reassigned to higher-performing initiatives.

Financial services firm: A mid-size bank runs annual PPM cycles aligned to its regulatory calendar. Every October, department heads submit project proposals. A portfolio committee scores each against five strategic pillars (customer experience, compliance, cost reduction, revenue growth, digital capabilities). Only projects scoring above a threshold threshold move to capacity review. The result: 60 proposals, 22 approved, 8 conditionally approved pending Q1 resource availability.

Manufacturing company: After a merger, the operations team inherits two overlapping ERP implementation projects from the two legacy companies. PPM process surfaces the duplication in the first portfolio review. One project is stopped, and its partially completed deliverables are folded into the surviving implementation, saving an estimated six months of redundant effort.

Benefits and challenges of PPM

Benefits

• Connects day-to-day project work to corporate strategy, so execution isn't just busy work.
• Prevents resource overload by making trade-offs visible before commitments are made.
• Reduces the number of zombie projects that limp along past their useful life.
• Creates a shared language between finance, operations, and IT when competing for budget.
• Improves forecast accuracy because the portfolio view surfaces dependencies and shared risks early.

Challenges

• Requires honest data. Scoring models only work if project sponsors don't inflate estimates to win approval. Political pressures on scoring are real.
• PPM processes can slow down fast-moving teams if governance adds bureaucracy without value. Keep the process proportionate to project size.
• The project life cycle view and the portfolio view use different cadences. Project managers think in sprints or phases; portfolio managers think in quarters. Bridging that gap takes deliberate effort.
• Organizational resistance. Stopping a project is a public admission that the original decision was wrong. Leaders who approved bad projects rarely champion the PPM process that surfaces them.

Best practices for PPM

Separate portfolio selection from project delivery. The people running projects should not be the same people approving them. Sponsorship bias produces portfolios stuffed with each department's favorite initiatives rather than the organization's highest-value work.

Score everything, even small projects. The instinct is to reserve PPM rigor for large initiatives. But small projects consume real resources and real attention. A portfolio full of 50 unchecked "quick wins" can block a single transformative project from getting the focus it needs.

Publish the portfolio publicly inside the organization. When every team can see which projects are active and why they were selected, political side-channels for sneaking new projects into the queue shrink. Transparency is a better governance tool than any approval form.

Build in explicit kill criteria at project authorization. Define at the start what conditions would cause the portfolio board to stop the project. Predefined exit criteria make mid-course stops feel like responsible decision-making rather than failure.

Treat the scoring model as a living document. Strategy changes. The weights in your scoring model should reflect current priorities, not what mattered three years ago when the model was first built.

Connect PPM to financial planning. The most effective portfolios are reviewed in the same rhythm as the annual budget and mid-year forecast cycles. PPM that runs on a separate calendar from finance will always lose the resource argument.

Frequently asked questions

What is the difference between project portfolio management and program management?

Program management coordinates a group of related projects that together deliver a benefit no single project achieves alone. Project portfolio management governs all projects and programs across the entire organization, optimizing the mix for strategic value and resource efficiency. A program sits inside the portfolio.

Who is responsible for PPM?

Typically a portfolio management office, a dedicated portfolio manager, or a steering committee of senior leaders. In organizations with a PMO, PPM is often one of the PMO's core responsibilities. For smaller organizations, a C-level sponsor may chair a quarterly portfolio review without a formal PMO structure.

How often should a portfolio be reviewed?

Quarterly is standard for most organizations. High-velocity businesses (startups, fast-growth tech) often review monthly. Heavily regulated industries may use a semi-annual cycle tied to regulatory planning windows. The review cadence should match how quickly the organization's strategic priorities shift.

What tools do companies use for PPM?

Dedicated PPM platforms include Planview, SAP Portfolio and Project Management, and Microsoft Project Online. Many mid-size organizations run effective portfolio reviews using a combination of a spreadsheet scoring model and a project status dashboard in their existing project management tool. The tool matters less than having a consistent process and honest data.

Can PPM work for agile organizations?

Yes. Agile PPM, sometimes called "Lean Portfolio Management" in the Scaled Agile Framework (SAFe), applies the same selection and prioritization logic but uses shorter funding cycles (often quarterly "PI" boundaries) and value stream budgets rather than project-by-project approvals. The core trade-off logic remains the same: pick the highest-value work the team can actually do.

---

PPM won't make every project succeed. But it dramatically improves the odds that the projects you run were worth starting in the first place. Start with a complete inventory, build a scoring model that reflects current strategy, and review the portfolio on a regular cadence. Those three habits alone will separate your organization from the majority that fund projects by inertia rather than intent.

Related reading

• Project Management Office (PMO)
• Program vs. Project Management
• Project Charter
• Risk Register
• Capacity Planning
• Resource Allocation
• Project Life Cycle