How Strategic Portfolio Management Evolved

Across the 2010s, enterprise organizations invested heavily in “going Agile.” Stand-ups, squads and value streams moved beyond individual software teams. Frameworks such as SAFe attempted to apply Agile principles across much larger organizations.

Organizations wanted shorter feedback loops, faster reprioritization and fewer decisions locked into long delivery cycles. But enterprise portfolios still operated within annual budgets, regulatory commitments, constrained specialist capacity and formal investment controls. Not every initiative could be funded, governed or delivered through the same cadence.

This tension influenced portfolio management as well as delivery. Agile Portfolio Management brought more adaptive planning and reprioritization into the portfolio. It did not remove the disciplines established through Project Portfolio Management.

Strategic Portfolio Management reflects the development of both.

This is not a clean history in which PPM was replaced by Agile Portfolio Management, which was then replaced by SPM. The disciplines overlap. The more useful story is how portfolio management expanded to accommodate both control and adaptability across increasingly hybrid enterprise portfolios.

For the full definition, governance model and implementation of SPM, see the Enterprise Guide to Strategic Portfolio Management.

PPM established the portfolio disciplines

Project Portfolio Management gave organizations a structured way to select, prioritize and govern investments across a portfolio.

Mature PPM already covered strategic alignment, financial management, resource allocation, dependencies, benefits and portfolio reporting. Strategy did not enter portfolio management with the arrival of SPM, and PPM should not be reduced to project status reporting.

For many organizations, however, the portfolio was still organized primarily around projects and programs. Annual planning, business cases, project funding and stage-gates provided the operating structure.

Those disciplines remain valid. A major transformation, regulatory program or capital initiative may still require exactly that model.

The pressure for something more adaptive grew as technology and digital functions adopted persistent teams, iterative delivery and shorter planning cycles. Portfolio management increasingly had to accommodate those models alongside established project structures.

Agile Portfolio Management made planning more adaptive

Agile Portfolio Management extended some of the principles associated with Agile delivery into portfolio planning.

Planning horizons shortened. Priorities could be revisited more frequently. Capacity was increasingly considered at team level rather than only through named project resources. Funding could follow persistent products or value streams rather than being tied exclusively to individual projects.

This changed an important assumption in portfolio management: an approved portfolio did not need to remain fixed until the next annual planning cycle.

But the enterprise did not become uniformly Agile.

A digital product could reprioritize quarterly while a regulatory program worked to fixed milestones. Persistent technology teams could coexist with time-bound projects. Finance could retain annual budgeting while the portfolio reviewed priorities during the year.

Agile Portfolio Management added useful practices for organizations operating in that environment. It did not provide a reason to discard financial controls, project governance or stage-gates where they remained appropriate.

The portfolio-management challenge became how to accommodate both.

SPM brings the disciplines together

Strategic Portfolio Management reflects that broader requirement.

It retains the financial control, governance, prioritization and capacity disciplines associated with PPM while incorporating more adaptive planning and reprioritization. It provides a portfolio model that can accommodate projects, products, programs and other investments without requiring them to follow the same delivery method.

SPM does not require an organization to choose between projects and products, Agile and stage-gated delivery, or annual budgeting and more frequent portfolio review. These models can coexist because they solve different operating problems.

Portfolio management sits above those choices. It provides the basis for comparing where capital and capacity are committed, how investments support strategic priorities, and whether those commitments should change as new evidence emerges.

That is where the evolution toward SPM has led.

PPM established the disciplines required to manage investment across a portfolio. Agile Portfolio Management made parts of that process more adaptive. SPM applies both across the mixed planning, funding and delivery models that now characterize many enterprise portfolios.