Strengthening PI Planning with Flow-Based Practices

PI Planning is one of the most visible and widely adopted elements of SAFe.

It brings teams together, aligns stakeholders, and creates a shared plan for the upcoming Program Increment. When it works well, it provides clarity and direction. When it doesn’t, it often becomes a high-effort event that produces plans which quickly drift from reality.

Rather than asking whether PI Planning should be replaced, a more useful question is:

How can we make PI Planning work as intended?

The Real Problem Is Not the Event

In most organizations, the challenges associated with PI Planning are well known:

  • Features are not ready
  • Dependencies are unclear
  • Teams are overcommitted
  • Priorities shift during or immediately after the event
  • Plans become outdated within weeks

These issues are rarely caused by the event itself.

They are caused by the condition of the system feeding into it.

If the ART Backlog is unstable (priorities constantly changing), if work items are too large, or are not ready to be executed, then even the best-run PI Planning event will produce unreliable outcomes.

A Flow-Based Perspective

A flow-based approach starts with a simple idea: The quality of the plan depends on the quality of the upstream intake system that feeds it.

Instead of relying on a periodic event to create alignment, flow-based practices focus on continuously regulating how work enters and moves through the system.

This includes:

  • Limiting work-in-progress
  • Managing aging work
  • Reducing feature size
  • Continuously refining and prioritizing the backlog
  • Using flow metrics to guide decisions

These practices do not replace PI Planning.

They strengthen it.

In organizations where backlog readiness is high, features are small, and flow is actively managed, PI Planning no longer needs to create a plan. It becomes a short alignment checkpoint.

Before PI Planning: Stabilize the Backlog

The most effective way to improve PI Planning is to improve the quality of the ART Backlog.

In many organizations, the backlog and the intake system are treated as the same thing. New ideas, requests, and partially understood work accumulate directly in the backlog, turning it into a large, unstructured inventory of demand.

This creates predictable problems:

  • Work enters PI Planning before it is ready

  • Features are too large or poorly understood

  • Priorities shift as new information emerges

  • Teams spend time interpreting work instead of delivering it

A flow-based approach separates these concerns.

The intake system is where ideas are evaluated, refined, and validated. It is a dynamic system where work is explored, shaped, and prepared.

The backlog serves a different purpose.

It is a pull queue of work that is continuously ready for delivery.

This distinction is critical.

The backlog is not a storage area for everything the organization might do. It is a curated pool of work that has already passed through intake and is ready to flow into delivery.

In practical terms, this means:

  • Only sufficiently refined and sized features enter the backlog

  • Work is small enough to flow predictably (typically no more than two sprints)

  • Priorities are continuously maintained

  • Dependencies are visible and manageable

  • Backlog items are ready to be pulled into delivery

Backlog readiness is not something that accelerates just before PI Planning. It is maintained continuous in a continuous state of readiness.

In many organizations, backlog readiness accelerates just before PI Planning because the event is approaching. This often leads to rushed decisions and incomplete understanding.

A flow-based approach removes that pressure by making backlog readiness a continuous activity rather than a last-minute effort.

During PI Planning: Shift from Commitment to Confidence

PI Planning is often framed around commitments. A flow-based approach reframes the conversation: Not “What can we commit to?”  But “What are we confident we can deliver?”

This shift is subtle but important. Confidence is grounded in:

  • observed delivery capacity
  • historical throughput
  • current work-in-progress

Planning becomes less about negotiation and more about understanding what the system can realistically achieve.

During PI Execution: Regulate the System

The most important work begins after PI Planning. Rather than treating the plan as fixed, flow-based practices introduce continuous regulation during execution.

This includes:

  • Monitoring WIP
  • Tracking feature aging
  • Identifying blocked work
  • Adjusting priorities based on new information

The ART Sync becomes more than a coordination meeting. It becomes a control point where the health of the system is reviewed and corrective action is taken.

PI Planning as a Checkpoint, Not a Control Mechanism

In a flow-based system, PI Planning still has value. But its role changes.

It becomes a checkpoint within a continuously managed system rather than the primary mechanism for coordinating work.

Alignment emerges from:

  • stable flow
  • clear priorities
  • continuous decision-making

not from a single event.

A Practical Path Forward

For organizations already using SAFe, this approach does not require structural change.

PI Planning remains.

Roles remain.

Cadence remains.

What changes is how the system is managed:

  • Backlog readiness becomes continuous
  • Flow metrics inform decisions
  • WIP and aging are actively managed and acted upon
  • ART Sync focuses on system behavior: delivery flow signals

One-Day Flow-Based PI Planning Agenda

One-Day PI Planning Agenda (Flow-Based)

1. Context & Priorities (60–90 min)
Business context, priorities, flow metrics
→ Shared understanding of direction and capacity

2. Backlog Readiness (45–60 min)
Validate top features (sized ≤ 2 sprints), readiness, dependencies
→ Clean, delivery-ready backlog

3. Team Breakouts (2–3 hrs)
Pull work based on throughput, split features, clarify scope
→ Realistic delivery plan

4. Dependency Alignment (60 min)
Resolve cross-team dependencies, adjust sequencing
→ Manageable coordination

5. Confidence Review (45–60 min)
Teams present plan, risks, confidence based on data
→ Shared delivery confidence

6. Final Adjustments (30 min)
Reprioritize, adjust scope, resolve issues
→ Aligned and achievable plan

Key Idea:
The backlog is ready. Work is sized for flow.
PI Planning confirms alignment—it does not create it.

PI Planning works best when it is supported by a stable, continuously managed flow of work.

By introducing flow-based practices, organizations can reduce planning risk, improve predictability, and make the event itself more effective. The reduction in duration is not the goal. It is a signal that the system is working.

The goal is not to eliminate PI Planning. It is to make it work as intended.

Scroll to Top