Field notes on running project portfolios. Written for PMO leads, portfolio managers, and the program teams who turn a list of projects into delivered outcomes.
Project portfolio management is the practice of choosing which projects to fund and which to stop, so that limited money and people go to the work that advances strategy. Here is what PPM means, what it involves, the benefits, and a worked example.
A steering committee is the small group of senior people who can fund, change, or stop a project. Here is what SteerCo means, who belongs on it, the decisions it owns, how often it should meet, and why most of them quietly turn into status meetings.
The project sponsor owns the business case, funds the work, and is accountable for the benefit. Here is the PMI definition, the responsibilities across the lifecycle, how the role differs from the project manager, and the four signs of a sponsor who has gone missing.
Project governance is the system of decision rights, forums, and escalation paths that controls a project. Here is what it means, the five components of a governance framework, a simple model you can copy, and where project governance ends and portfolio governance begins.
Lean portfolio management aligns strategy and execution by funding value streams instead of projects. Here are the three dimensions, lean budgets and the four guardrails, the portfolio Kanban, what changed with AI-Native SAFe in 2026, and how LPM really differs from traditional PPM.
Project management delivers a single piece of work well. Project portfolio management decides which work gets funded in the first place. Here is the difference in scope, ownership, funding, and success measures, plus where programs sit between the two.
A PMO earns its place by making decisions better, not by collecting status. Here are twelve PMO best practices that hold up in real organizations, a checklist you can audit yourself against, and the failure patterns that get project management offices disbanded.
Dependency mapping is how you make the links between work visible before they turn into slippage. Here is the five-step process, a template you can copy, a worked example, an honest look at the tooling, and how to run the mapping workshop that produces most of the value.
Twenty five worked examples of project dependencies, sorted by type: mandatory, discretionary, internal, external, and cross-project. Each one includes what it looks like in a plan and what to do about it once you have found it.
IT portfolio management covers three portfolios, not one: projects, applications, and infrastructure. Here is how the pieces fit, how the TIME model and run-grow-transform actually get used, and where IT PPM differs from ordinary project portfolio management.
There is no current Gartner Magic Quadrant for Project and Portfolio Management. The last one was published in May 2019, and the market now sits in two reports: Strategic Portfolio Management and Adaptive Project Management and Reporting. Here are the PPM tools named in their 2026 editions, what each report covers, which one to read, and how to use it without letting it choose for you.
A PMO analyst collects, cleans, and interprets project data across a portfolio, builds the reporting leadership relies on, and spots the project that is slipping before it turns red. Here is what the role involves day to day, a job description you can adapt, the skills that matter, and how it differs from a project manager and a business analyst.
One account for the handbook and the template pack. Enter your email and we send a 6-digit code to confirm it.
No card needed. One email when something worth reading ships, and you can leave with one click.