SAFe 6.0: The ART Backlog

Topics covered:

The role of the ART Backlog.
Customer Centricity
ART Backlog Refinement and PI Planning Readiness.
ART Backlog Ranking using WSJF.

The Role of the ART Backlog

An ART Backlog is a stack-ranked list of deliverables – product features and supporting technology infrastructure items – targeted for the next PI. The ART Backlog is the single source of work for an Agile Release Train (ART). An ART is an organizational arrangement designed to support a value stream. We will have one ART Backlog per value stream. In preparation for PI Planning, ART backlog items must be sufficiently refined and stack-ranked by business value. The ART Product Manager is responsible for creating and managing the ART Backlog.

The ART Backlog may be derived from multiple sources including a Portfolio Backlog or a product strategy (sometimes laid out as a Product Roadmap). Ultimately, everything in the ART Backlog exists to support the realization of the Product Vision and strategy. Alignment with the portfolio backlog is reflected in the ART Backlog.

The time and effort needed for PI planning will depend on the refinement of this backlog. This is a critical step for PI Planning success and will be the focus for this chapter.

The general flow from Product Vision to Product Backlog can be represented as:

For our purposes we will use the following definitions:

Enterprise Vision: is a forward-looking, aspirational statement defining what a company or enterprise aims to become, focusing on future growth, global competitiveness, innovation, and sustainable prosperity. The Enterprise Vision provides directional intent and constraints that guide strategic choices, investment decisions, and prioritization across the portfolio.

Strategic Themes: are a small set (typically 3–5) of enduring focus areas (like “Customer Delight” or “Digital Innovation”) that translate the Enterprise Vision into actionable strategic intent. They provide context for decision-making by expressing where the organization must invest and excel to achieve its vision. Strategic Themes guide portfolio investment decisions, economic prioritization and trade-offs between competing initiatives. Strategic Themes act as persistent lenses through which work is evaluated, ordered, and pulled—ensuring continuous alignment without requiring centralized planning events. Strategy sets direction and constraints, not delivery commitments.

Portfolio Backlog: Portfolio management is where strategy is translated into investment decisions. The Portfolio Backlog is an ordered set of portfolio-level initiatives (epics) that express strategic intent as investment hypotheses rather than delivery commitments. It reflects how the enterprise allocates investment across value streams in pursuit of its Strategic Themes. Owned by Lean Portfolio Management, the Portfolio Backlog functions as the upstream flow system that: Translates strategy into prioritized investment options, Applies WIP limits to strategic bets and allocates funding to value streams rather than projects. Portfolio epics flow into value streams when they are economically justified and ready to be explored and executed—not when a planning cycle begins.

ART: A value stream-aligned organization model where work is organized around meeting customer needs vs. internal silos.

ART Backlog: The ART Backlog is where strategy meets execution. ART Backlog items elaborate portfolio epics into outcome-oriented features and enablers, making business intent inseparable from the work itself. The ordering of the ART Backlog is the primary alignment mechanism between strategy and delivery. There is one ART backlog for each Value Stream in the portfolio. (Exception: very large value streams may need multiple ARTs). The ART backlog contains the highest priority items needed to support the strategy. ART Backlog items will have been refined and stack ranked as a prerequisite step to support PI Planning.

One can see that solution delivery flows through a series of interconnected backlogs from strategy to delivery, from epics to features to user stories.

Strategic Alignment in SAFe:

Strategic Theme: Expand into autonomous delivery.
Epic: (Portfolio Backlog): Design and build a fully functional autonomous delivery vehicle prototype within six months. And Achieve 90% successful autonomous deliveries in a controlled test environment. (Typically, multiple PIs).
ART Backlog: Feature or App to enable customers to track and interact with autonomous deliveries. (Features scoped to fit in a single PI).
ARTs: Organizational model designed to support Value Streams: organize work around customer needs, rather than internal silos.

ART Backlog Refinement

There is no single best way for refining the ART Backlog, however SAFe does recommend an approach based on an Intake Kanban. What follows is one example.

The goal is to provide a continuous flow of ready work to the ART Backlog. Features that evolve to the ART Backlog state are considered sufficiently well-defined for PI Planning and delivery.

Key states in the intake workflow:

Funnel: Initial placeholder for proposed features. Features may be pulled here from epic definitions in the Portfolio Backlog, or directly from other sources.

Business Review: Features are reviewed for alignment with strategy, product vision and customer needs, and may be rejected if not considered a good fit. Upon exit from this state features should be more formally defined with stated benefits and acceptance criteria (see below on business value drivers and KPIs). Features are given an initial ranking relative to other features in the backlog based on business value and estimated development effort. (More below).

Technical Analysis: Technical review and analysis led by the System Architect. An outline implementation approach is identified together with any additional ‘architectural runway’ or ‘enabler’ items. Feature size estimate is updated based on additional information from technical analysis. Omission or skimping of this step can lead to serious problems in the execution of the PI. Teams need to be able to hit the ground running once the PI commences, and not be required to invest large amounts of time in solving major architectural questions during the PI.

Ranking: Feature ranking is determined objectively using Weighted Shortest Job First (WSJF, or other equivalent method). Basically, the numerator (business value and other factors) and denominator (feature size or cost estimate) are both estimated relative to all other features in the backlog using Fibonacci. The resulting rank is calculated as the ratio of business value / size (cost).

ART Backlog: Features have completed all workflow steps, and are fully defined with benefits (business outcomes), acceptance criteria, and architectural dependencies, and have been ranked with respect to all other features in the ART Backlog. These features are considered ART Backlog items, and ready for PI Planning and delivery.

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.

Just as delivery teams continuously refine their backlogs ahead of sprint planning, ART Backlog refinement is intended to be a cadenced event (vs. a single big-bang planning event) that runs continuously throughout the PI cycle. The event is led by the Product Manager. Attendees should include all team PO’s, Architects and business stakeholders who can contribute to moving feature requests across the Kanban board by contributing increasing amounts of detail about each feature. The goal is to have at least one PI’s worth of ready features available at least 2-4 weeks ahead of the next PI Planning event.

The Minimum Information Model

Features do not have to be perfectly defined to qualify for the ART Backlog and be ready for delivery, but they must carry enough information to support three things:

Understanding — What is being built and why
Prioritization — Why this work matters relative to other work
Evaluation — How we will know if it was successful

The exact format is not important. What matters is that these signals are present.

A practical way to achieve this is to define a minimal information model for each feature.

Example: ART Backlog Feature

A feature entering delivery might include the following:

Feature Description
A clear description of what is being delivered and the problem it addresses.

Problem or Opportunity
The signal or condition that triggered this feature, such as customer feedback, operational data, or a strategic initiative.

Expected Outcome (KPI)
A measurable outcome that should change if the feature is successful.

For example:

reduce cycle time
increase conversion rate
improve customer satisfaction
reduce defect rates

This expresses the feature as a testable hypothesis.

(Business) Value Driver
The reason this work matters from a business perspective.

Examples include:

revenue growth
cost reduction
risk mitigation
customer retention

Acceptance Criteria
The conditions that define when the feature is complete.

This ensures that delivery work remains scope-bounded and testable.

Readiness Criteria
Evidence that the feature is ready to enter the delivery system.

For example:

validated through discovery
sufficiently small to complete within a short timeframe
dependencies identified

Features as Hypotheses

A feature is not just a unit of work. It is a hypothesis about improving the system.

A simple way to express this is: If we deliver this feature, then [KPI] should improve by [expected amount].

This framing connects the ART Backlog directly to the discovery system and ensures that delivery work remains tied to measurable outcomes.

When the ART Backlog enforces a minimal information model, it protects the delivery system from upstream variability.

Only work that is:

understood
validated
economically meaningful

is allowed to enter delivery. This creates a stable, pull-based system where teams can focus on completing work rather than constantly clarifying or reprioritizing it. The ART Backlog can be viewed as a control mechanism. That is, it regulates the flow of work from discovery to delivery.

Without this boundary, discovery and delivery collapse into a single overloaded system. Work is started before it is ready, priorities shift continuously, and flow breaks down.

With it, the system becomes predictable and self-regulating.

Here is a possible template you might use in support of the above guidance:

Feature	High Quality Product Images
Description	Provide high resolution product images from multiple perspectives
Benefits	Good quality images are a key determinant to move products on eCommerce websites and increase conversion rates and sales.
Acceptance Criteria	Image resolution at least 300 pixels per inch Multiple images showing the various perspectives of the item such as front, side, underneath, Image size of either 640×640 or 800×800 pixels but use consistent size for all images. Ability to zoom in on a specific piece of the object and to capture only one detail of the whole photographed product. Change product image on hover which allows customers to view another image of product by just hovering. Thumbnails also provided of 200×200 pixels
Business Value Driver	Increase revenue per visitor
KPI (Measurable outcome)	Improve Conversion Rate by X%

ART Backlog Ranking With WSJF

ART Backlogs should be stack-ranked – not simply prioritized. This is all about realizing the highest value at the earliest opportunity and minimizing work in progress. Many product owners and their teams simply prioritize features as High, Medium, or Low priority. Inevitably, we frequently end up with multiple high priority features, which offers little guidance on delivery sequencing. This results in teams having multiple backlog items in progress at the same time which can delay getting any individual feature to done. Further, it also delays getting feedback from users and stakeholders on finished work, which impedes the ability to iterate, adapt and continuously innovate. Limiting WIP by having an objectively ranked and sequenced backlog is the key to optimal delivery lead times.

By adopting the practice of rank-ordering the ART Backlog, the team has total clarity about which item they should be working on. When work on the highest ranked item is done, the team moves to the next item on the list. When things change, resulting in re-ranking items or even adding new ones, that is not a problem because the team can finish the current item and now has the flexibility to start working on something else.

Feature ranking is done on a relative basis against other features in the backlog. One technique for doing this is Weighted Shortest Job First (WSJF). WSJF is basically a scheduling algorithm that strives to ensure features of highest value and lowest cost (lowest consumption of development capacity) are ranked highest for delivery.

Weighted Shortest Job First (WSJF) Ranking

Weighted Shortest Job First (WSJF) is a technique first popularized by Don Reinertsen in his book: The Principles of Product Development Flow. It provides a method to prioritize a list of features or initiatives in an objective way based on business value and relative return on investment. Each feature is scored based on its Cost of Delay divided by its size or development effort.

How is WSJF calculated?

WSJF = Cost of Delay (COD)/Effort, where

COD = Business Value + Time Criticality + Risk Reduction Opportunity
Rank = COD/Effort

WSJF parameters for each feature are scored relative to all other features using the Fibonacci Series (1, 2, 3, 5, 8, 13 …):

The underlying rationale for WSJF is 2-fold:

Prioritize work that has the highest cost of delay or highest overall value in terms of business value, time criticality and risk reduction.
When all jobs have the same delay cost, or same overall value, do the one with least effort first (The fastest way to realize value).

More on WSJF here, including sample calculations.

ART Backlog Creation Checklist

A Feature Intake Kanban system has been setup, and supports the definition, analysis, and readiness of features for addition to the ART Backlog.
Architects are engaged throughout the intake process to ensure additional architectural runway and any required technical enablers are defined.
ART Backlog features have been ranked using WSJF.

With an ART Backlog comprising a ranked list of ready features, we are now ready for PI Planning.

For more, get the book at Amazon: SAFe PI Planning: A Step-By-Step Guide

Book Contents:

Chapter 1. Introduction to the Scaled Agile Framework. This provides an overview of the SAFe framework.
Chapter 2. Organizing for scaled delivery. Describes the organizational prerequisites for successful SAFe adoption.
Chapter 3. Constructing an ART Backlog. The ART Backlog is the starting point for PI Planning. This chapter describes how to create a backlog that is aligned with product vision and strategy and has product features sufficiently well-refined to support PI Planning.
Chapter 4. PI Planning Step-By-Step, takes you through each of the basic steps of planning a PI.
Chapter 5. PI Execution Practices explains the essential roles, practices, and artifacts necessary for successful execution and delivery throughout a PI.

Get the book from Amazon!