Strategy → Portfolio → ART Backlog → Delivery

One of the most common failure modes I see in large-scale Agile transformations is not poor execution—it is broken flow between strategy and delivery.

Strategy lives in decks.
Portfolio decisions live in committees.
Backlogs live with teams.
Alignment is attempted every few months in a large planning event.

When these elements are disconnected, planning has to compensate. That is why PI Planning becomes overloaded—and why it feels indispensable even when it is painful.

This post outlines a flow-based alternative: a coherent, end-to-end model that connects strategy to delivery through continuous flow rather than episodic planning.

The Core Idea

Alignment should not happen in a meeting.
It should be expressed continuously through the work itself.

In a flow-based system, strategy, portfolio decisions, and delivery are not separate layers—they are different horizons of the same value flow.

The model looks like this:

Strategy → Portfolio → ART Backlog → Pull

Each step narrows intent, increases fidelity, and preserves optionality—without relying on time-boxed planning events to stitch things back together.

1. Strategy: Direction, Not Plans

Strategy sets direction and constraints, not delivery commitments.

Its purpose is to answer:

  • Where must we win?

  • What outcomes matter?

  • What trade-offs are we willing to make?

In a flow-based model, strategy does not decompose directly into plans or dates. Instead, it provides persistent context that informs every downstream decision.

Good strategy enables prioritization.
It does not attempt to predict delivery.

2. Portfolio: Strategy Becomes Investment Flow

Portfolio management is where strategy is translated into investment decisions, not scope commitments.

This is the critical reframing.

Rather than acting as a governance layer “above” delivery, portfolio management becomes the upstream stage of flow, where:

  • Strategic intent is expressed as investment hypotheses

  • Work is prioritized economically

  • WIP limits are applied to strategic bets

  • Funding is allocated to value streams, not projects

Portfolio epics are not promises.
They are options to invest.

Only when an epic is sufficiently understood and economically justified does it become eligible to flow downstream.

3. ART Backlog: Strategy Meets Execution

The ART Backlog is where strategy becomes actionable delivery intent.

Each value stream owns its ART Backlog, which contains:

  • Outcome-oriented features

  • Architectural and technology enablers

  • Explicit ordering based on economic priority

  • Clear readiness policies

Outcome-oriented features are product capabilities designed to achieve specific, measurable business results or user behaviors (outcomes) like increased retention, conversion, or satisfaction, rather than just listing outputs (features) or tasks; they focus on why something is built (value) to drive strategic alignment and impact, moving beyond mere completion to deliver actual positive change for customers and the business

In a flow-based system, the ART Backlog is continuously refined and continuously ordered.

This is a critical shift:

  • The backlog is not prepared for a planning event

  • The backlog is the alignment mechanism

When the ART Backlog is trusted:

  • Business intent is embedded in the work

  • Priority is visible at all times

  • Teams do not need objectives written after the fact to explain what matters

4. Pull: Alignment Through Action

Pull is where alignment becomes real.

Instead of committing to speculative plans weeks or months in advance:

  • Teams pull the next highest-value work when capacity is available

  • Work is decomposed just in time

  • Learning feeds directly back into prioritization

Pull replaces promises with responsiveness.

Alignment is expressed every time a team pulls the next item from the top of the ART Backlog.

Why This Reduces the Need for Centralized Planning

In traditional implementations, PI Planning carries an enormous burden:

  • Resolving priority conflicts

  • Negotiating dependencies

  • Translating strategy

  • Creating delivery certainty

That burden exists because flow is broken upstream.

When strategy flows through portfolio decisions into a trusted ART Backlog:

  • Alignment is continuous

  • Dependencies are reduced rather than negotiated

  • Predictability is demonstrated through throughput, not declared through objectives

PI Planning may still exist—but it stops being the operating system.

It becomes a lightweight alignment checkpoint, not the primary coordination mechanism.

The Shift in Leadership Questions

This model changes the questions leaders ask.

Instead of:

  • “What did we commit to for the next PI?”

Leaders ask:

  • “What is next in the backlog, and why?”

  • “How reliably do we deliver?”

  • “What happens if priorities change?”

Those are better questions—and they lead to better decisions.

Closing Thought

Planning is not the enemy.
But planning should not be doing the work of structure, strategy, and flow.

When strategy flows into portfolio decisions, into backlogs, and into pull:

  • Alignment becomes continuous

  • Trust becomes empirical

  • Planning becomes optional

That is what it means to move beyond PI Planning—without losing control, predictability, or intent.

Scroll to Top