SAFe Model

SAFe, modelled, not simulated.

Levels, hierarchy, work item types and Program Increments are part of the product’s model, not labels on a generic tracker.

1 · Spaces and levels

Pick a level. Everything downstream follows.

PortfolioEpic
  1. Funnel
  2. Reviewing
  3. Analyzing
  4. Portfolio Backlog
  5. Implementing
  6. Done
Large SolutionCapabilityOptional tier
  1. Funnel
  2. Analyzing
  3. Solution Backlog
  4. Implementing
  5. Validating
  6. Done
ARTFeature
  1. Funnel
  2. Analyzing
  3. ART Backlog
  4. Implementing
  5. Validating
  6. Done
SquadUser Story
  1. To Do
  2. In Progress
  3. In Review
  4. Done
Levels, work items, default stages and default boards
LevelWork itemDefault stagesDefault boards
PortfolioEpicFunnel → Reviewing → Analyzing → Portfolio Backlog → Implementing → DoneBacklog, Board, Gantt
Large SolutionCapabilityFunnel → Analyzing → Solution Backlog → Implementing → Validating → DoneBacklog, Board, Gantt, Program Board
ARTFeatureFunnel → Analyzing → ART Backlog → Implementing → Validating → DoneBacklog, Board, Program Board, PI Timeline
SquadUser StoryTo Do → In Progress → In Review → DoneBacklog, Scrum, Board, Calendar

2 · The hierarchy

Every Story rolls up to its Epic

Work items link upward to a parent on the level directly above, so a Story rolls up into its Feature, Capability and Epic. The server guarantees the chain cannot be broken or looped.

Hierarchy: Portfolio (Epic) to Large Solution (Capability, optional) to ART (Feature) to Squad (User Story, Bug, Task, Sub-task, Spike)PortfolioEpicLarge SolutionCapability · optional tierARTFeatureSquadUser Story · Bug · Task · Sub-task · Spike
  1. Portfolio
    Epic
  2. Large Solution
    Capability · optional tier
  3. ART
    Feature
  4. Squad
    User Story · Bug · Task · Sub-task · Spike

3 · Work item types

A level says how big an item is; a type says what it is for.

Enablers exist at every level, in four categories: explorationarchitecturalinfrastructurecompliance

LevelTypesAlso available
PortfolioEpicEnabler
Large SolutionCapabilityEnabler
ARTFeatureEnabler
SquadUser Story, Bug, Task, Sub-task, SpikeEnabler

4 · Parents versus dependencies

Vertical rolls up. Horizontal coordinates.

Parent

Vertical, and drives rollups. A child links to one parent on the level directly above.

Dependency

Horizontal, between squads on the same train, drawn on the planning wall: blocks / is blocked by, duplicates, clones, relates to.

5 · Program Increments

A PI contains its sprints

A work item is scheduled into one iteration and assigned to one team.

6 · Beyond the framework

Your organisation is not a template

Custom spaces

Standalone, nested under a SAFe space, or acting as a level.

Custom work item types

Add the types your teams need, with their own workflows and pages.

SAFe® and Scaled Agile Framework® are registered trademarks of Scaled Agile, Inc. WS Crafter is not affiliated with or endorsed by Scaled Agile, Inc.

See the SAFe model with your own train in mind.

Request a demo