Portfolio Ways of Working

Updated 27 March 2026

The portfolio level is a governance and investment function, not a delivery organization. Its ways of working reflect that distinction: the rhythm is driven by decision cadences, not delivery cycles. Where teams operate on sprint cadence and DVSs operate on PI cadence, the portfolio operates on a slower strategic rhythm — with regular touchpoints that maintain visibility over the initiative pipeline and keep investment decisions connected to organizational strategy.

The portfolio management function works continuously, not only at scheduled meetings. Portfolio Kanban is an ongoing system. Initiatives move through it as understanding develops and capacity becomes available. The forums described here are the structured decision points within that continuous flow.

The Portfolio Governance Cadence

Portfolio governance operates at two cadences simultaneously: a continuous flow cadence tied to Portfolio Kanban activity, and a periodic strategic cadence tied to planning horizons and PI boundaries.

The two cadences serve different purposes. The continuous cadence ensures initiatives move through the pipeline without stalling — reviews happen when they are needed, not only at scheduled intervals. The periodic cadence creates regular alignment points where portfolio direction is reviewed against organizational strategy and delivery reality.

The cadence frequency for Portfolio Sync and Agile Portfolio Review depends on the organization’s PI length and governance needs — the ranges above reflect typical practice.

Portfolio Kanban Review

The Portfolio Kanban review is not a single scheduled meeting — it is the ongoing governance work of the portfolio management function. Initiatives require active attention at two key transition points: entering Analyzing (is this worth a full business case?) and exiting Analyzing (is this worth funding?).

These go/no-go decisions are the primary governance mechanism at portfolio level. They should happen when the initiative is ready — not only when a governance calendar permits. A portfolio that queues initiatives for monthly approval meetings creates artificial delay and signals that the decision-making function is not operating continuously.

Between these decision points, the portfolio management function monitors active initiatives: reviewing progress, assessing whether value hypotheses are holding, and making explicit decisions to continue, pivot, or stop. Initiatives in implementation do not manage themselves. Regular, lightweight check-ins — not heavy steering committees — keep portfolio governance active without overloading it.

See: Portfolio Kanban Flow for stage definitions and exit criteria.

Strategic Portfolio Review

The Strategic Portfolio Review is a periodic event — typically aligned to PI boundaries or quarterly — where the portfolio management function steps back from individual initiative decisions and reviews the portfolio as a whole.

The purpose is strategic coherence: ensuring that what the portfolio is funding and delivering remains aligned with organizational priorities as those priorities evolve. The questions addressed are not operational (“is initiative X on track?”) but directional (“is the portfolio mix still the right investment given what we know today?”).

The Strategic Portfolio Review typically covers:

Portfolio health. How is the initiative pipeline moving? Where are items stalling? What does flow time and WIP age data indicate about the system’s health? This is the point at which flow metrics inform strategic decisions — not as a reporting exercise, but as a signal about whether the investment system is functioning.

Strategic alignment check. Are the initiatives currently being funded still aligned with the organization’s strategic themes? Have priorities shifted in ways that require resequencing the backlog or stopping active initiatives?

Capacity and value stream alignment. Is the demand on value streams reasonable? Are there initiatives queued in the Portfolio Backlog that cannot realistically start because value streams are at capacity? Are the right value streams funded at the right levels for the coming period?

Investment decisions. Are there initiatives that should be stopped, accelerated, or resequenced based on what has been learned since the last review?

The Strategic Portfolio Review is an active decision meeting, not a status update. It produces explicit decisions: approvals, stops, resequencing, and funding adjustments. Decisions made here are the primary mechanism through which organizational strategy becomes delivery reality.

Portfolio Sync

Between Strategic Portfolio Reviews, the Portfolio Sync maintains operational visibility over the running portfolio. This is a shorter, more frequent forum — monthly — focused on current pipeline activity and emerging issues.

The Portfolio Sync covers:

• Portfolio Kanban status — are Initiatives moving? Where are items stalling?
• LBC health check — does the hypothesis still hold for active Initiatives? Continue, pivot, or stop?
• Budget guardrails — are spending patterns within defined boundaries?
• Pre-PI preparation — which Initiatives are candidates for the next PI, and is the portfolio management function ready to make that sequencing decision?
• Portfolio-level blockers — what requires escalation or decision above DVS level?

Keeping the LBC alive

An approved Lean Business Case is not a blank check. The Initiative Owner is responsible for the Initiative throughout its lifecycle. At each Portfolio Sync, active Initiatives are reviewed against three questions drawn from the original LBC:

• What did we expect?
• What have we seen so far?
• Continue, pivot, or stop?

This is not a formal re-approval process. It is an active monitoring practice that keeps investment decisions honest. An Initiative whose hypothesis is no longer supported by evidence should face an explicit decision — not continue by default because no one has formally stopped it.

Agile Portfolio Review

The Agile Portfolio Review is a structured forum at PI or quarterly cadence. It is a feedback loop between delivery outcomes and portfolio investment decisions.

Where the Portfolio Sync maintains operational visibility over the running pipeline, the Agile Portfolio Review steps back to ask whether the portfolio’s investments are producing the expected results.

The forum covers:

Delivery results. What did active Initiatives produce in the past PI or quarter? Is the hypothesis being validated? Where is evidence accumulating that a pivot or stop decision is warranted?

Budget status. Are spending patterns within guardrails? Are there value streams that are over- or under-resourced given current priorities?

Re-prioritization. Given what was learned, should any Initiatives be resequenced, accelerated, stopped, or added to the Portfolio Backlog?

The Agile Portfolio Review produces explicit decisions — not status awareness alone. Initiatives that are not producing expected outcomes should face a conscious continue, pivot, or stop decision here, not drift into the next period by default.

Portfolio Management Function at PI Planning

At PI Planning, the portfolio management function is an input provider, not a delivery planner. DVS teams plan the details. The portfolio management function provides the strategic context those plans should respond to.

Its role at PI Planning:

• Present business context — current market conditions, strategic priorities, and direction
• Share the prioritized Initiative list and top-priority Features as input to DVS teams
• Communicate strategic themes and budget guardrails
• Participate in Management Review and Problem Solving (typically the second day of PI Planning)

Portfolio-level participants do not plan delivery at PI Planning. Decisions about how to implement Initiatives belong at DVS and team level.

Prioritization

Approved initiatives in the Portfolio Backlog are sequenced using a portfolio-adapted prioritization model grounded in economic value and cost of delay. See Initiative Prioritization for how the framework is applied and what factors drive sequencing decisions at portfolio level.

Connection to DVS and PI Cadence

The portfolio cadence and the DVS PI cadence are not independent. They must be synchronized at key points: when new initiatives are approved and sequenced into DVS backlogs, and when portfolio-level decisions require input from delivery reality.

The primary connection point is the PI boundary. The Strategic Portfolio Review is most useful when aligned to the PI cadence — immediately after a PI’s Inspect & Adapt, portfolio leadership has fresh information about what was delivered, what was learned, and what capacity looks like for the next PI. That information feeds directly into portfolio sequencing decisions.

The Value Stream Owner is the structural link between the two levels: participating in portfolio governance while remaining connected to DVS operations. This role is the primary channel through which portfolio priorities are translated into DVS delivery commitments — and through which DVS delivery reality is visible to portfolio leadership.

See: DVS Ways of Working for the DVS-level cadence that portfolio governance frames and funds.