Scaled Agile Framework — Interactive Workflow

Organizational strategy translated into portfolio-level direction. Includes Strategic Themes, OKRs, and Portfolio Vision that guide investment decisions and ART priorities.

Epics flow through the Portfolio Kanban system (Funnel → Reviewing → Analyzing → Ready → Implementing → Done). Prioritized by WSJF. Epic Owners shepherd epics through.

Manages Epic flow from ideation through implementation. Columns: Funnel → Reviewing → Analyzing → Ready → Implementing → Done. WIP limits at each stage prevent overloading ARTs.

The primary organizing construct. Development value streams build solutions; operational value streams deliver them. ARTs operate within value streams. Epics flow through to reach customers.

Product Management defines the product vision and roadmap. The vision describes the future state; the roadmap plots the journey across multiple PIs. Presented at PI Planning.

Features and Enablers prioritized by WSJF. Owned by Product Management. Top items are refined and ready for PI Planning. Includes NFRs from System Architect.

Key stakeholders responsible for fitness-for-use, governance, and ROI. Assign business value to PI Objectives, participate in PI Planning, evaluate outcomes at System Demos and I&A.

Owns the ART Backlog, defines product vision and roadmap, prioritizes features using WSJF, presents at PI Planning. The voice of the market at ART level.

Defines overall architecture, identifies NFRs, maintains architectural runway, guides technical decisions across the ART. Presents architecture vision at PI Planning.

Release Train Engineer — servant leader and chief coach for the ART. Facilitates PI Planning, ART Sync, I&A, and System Demos. Manages cross-team dependencies, optimizes flow.

A long-lived team of Agile Teams (50–125 people) that incrementally develops and delivers solutions. Operates on a fixed PI cadence. The primary value delivery construct in SAFe.

SAFe’s signature 2-day event. All ART members align on vision, identify dependencies, commit to PI Objectives, build the ART Planning Board. Produces alignment impossible through documents.

First 2-week iteration. Teams execute Sprint plans, integrate continuously, demo at System Demo. Daily Stand-ups, Iteration Planning, and Reviews happen within.

Second iteration. Teams continue delivering stories and features. System Demo integrates work across all teams. ART Sync and Coach Sync maintain coordination.

Third iteration. Feature completion accelerates. Architectural runway maintained. Teams may release value mid-PI through Release on Demand.

Final development iteration before IP. Teams finalize features, prepare for PI System Demo. Focus shifts to integration completeness.

System Demo after Iteration 1 — ART demonstrates the integrated solution increment to stakeholders. Objective evidence of progress.

System Demo after Iteration 2 — growing integration and feature completeness visible to stakeholders.

System Demo after Iteration 3 — substantial PI progress demonstrated.

System Demo after Iteration 4 — near-complete PI increment demonstrated.

Innovation & Planning iteration — dedicated time for innovation, hackathons, training, infrastructure, and next PI Planning preparation. Buffer for PI commitments.

Inspect & Adapt — PI System Demo, quantitative/qualitative review, and problem-solving workshop. Produces improvement items for the next PI.

Cross-functional team of ~10 using SAFe Scrum or Kanban. Includes Product Owner (story content authority), Scrum Master/Team Coach (facilitation & coaching), and Developers.

Another Agile Team. Teams coordinate through shared events (PI Planning, System Demo) and sync events (ART Sync, Coach Sync, PO Sync).

ARTs typically contain 5–12 Agile Teams. Each delivers stories contributing to features. Teams collectively produce the integrated solution increment.

Each team maintains their own backlog of user stories decomposed from features. Owned by the Product Owner. Includes stories, defects, enablers, and improvement items.

Continuous Exploration (what to build) → Continuous Integration (build & test) → Continuous Deployment (release on demand). The technical backbone enabling flow.

The ultimate recipient of value. Products released on demand through the Continuous Delivery Pipeline. Feedback flows back through Sprint Reviews, System Demos, and I&A.

Value can be released at any time — not just at PI boundaries. The Continuous Delivery Pipeline enables release when business conditions are right.

Foundational practices: SAFe Scrum (iterative delivery), SAFe Kanban (flow management), Built-in Quality (shift-left, TDD, pairing, DoD), DevOps (CALMR).

Weekly coordination: Coach Sync (SM/TC alignment), PO Sync (scope alignment), ART Sync (combined). Keeps the train coordinated between PI Planning events.