Skip to Content
DocsPortfolioOverview

Portfolio

Updated 27 April 2026

The portfolio level is a governance and investment function. Its job is to decide what to fund, align delivery capacity to strategic direction, and continuously validate that active investments remain sound as circumstances evolve.

This page is an entry point. The sections below — organization, ways of working, flow, goals, metrics, needs — are not components of the portfolio level. They are recurring dimensions that exist at every level of the delivery system. What is specific to portfolio is what each dimension contains here: who governs, how decisions are made, what flows through the system, how outcomes are measured.


Capability

Agile Portfolio Management — The complete capability map for portfolio-level governance: from strategic goal management and financial governance through investment prioritization to outcome measurement.


Organization

How the portfolio level is structured and who does what.


Ways of Working

How the portfolio level operates — its forums, cadences, and decision mechanisms.

  • Portfolio Ways of Working — Portfolio Kanban Review, Portfolio Sync, Agile Portfolio Review, and Strategic Portfolio Review

Flow

How initiatives move through the system.

  • Portfolio Kanban Flow — Stage definitions, entry and exit criteria, and WIP governance for the initiative pipeline

Goals

How strategic direction is set and tracked.

  • Outcome Goals — How OKRs and strategic themes are used to anchor portfolio decisions

Metrics

How portfolio health, outcomes, and investments are measured. Several metric dimensions operate at portfolio level — none replaces the others.

Flow metrics — How efficiently initiatives move through the system: flow time, WIP age, throughput, predictability. Diagnose whether the investment pipeline is healthy.

Business outcome metrics — Whether what was funded is producing the expected results: KPIs, KRAs, and KRIs measured against the strategic goals each initiative was approved to pursue. (Dedicated reference page in development.)

Other dimensions — such as portfolio maturity and capability development — may be developed as the model evolves. Not every dimension needs its own page; some are diagnostic companions to those above.


Needs

The artifact type that flows through the portfolio system.

  • Initiative — What an Initiative is, what it contains, and how it moves through the pipeline