Sample data. Every number, team, feature and date on this page is fictional (Phoenix ART and its teams are made up). Almost everything is read automatically from Jira Align / Jira / Azure DevOps and the CI/CD pipeline; the only manual inputs are business value scores set by Business Owners at PI Planning and ROAM status at the risk review.
Contents
Team
ART & PI overview
PI objectives & predictability Committed vs uncommitted, business value planned vs actual
ART predictability by PI (target ≥ 80%)
What it tells an RTE: SAFe treats 80–100% predictability as healthy. Below 80% means the train over-commits; consistently 100% can mean it under-commits. Uncommitted objectives are stretch work.
Team capacity vs load per iteration
CapacityPlanned load
Capacity comes from team calendars and normalized velocity; load is the sum of story estimates per iteration. Iterations above 100% are where spillover and dependency slips usually start.
Feature burnup Accepted feature points vs total scope
AcceptedTotal scope
Scope grew 7.6% since PI Planning. At the current rate the ART lands about 205 of 226 points by the end of I5.
Program board & cross-team dependencies Pulled from issue links; nothing entered by hand
ROAM risks Resolved, Owned, Accepted, Mitigated
Iteration velocity per team Accepted story points
Velocity is for each team's own planning; story points are not comparable across teams. Watch trend and stability.
Release & milestone calendar
Flow metrics SAFe flow metrics computed from work item history
Flow distribution
Flow time by PI (median days)
Metric definitions & thresholds
Definitions follow SAFe 6.0 measure-and-grow guidance; tune thresholds to your train.