Scaling with ARTs
For organizations running SAFe at scale, AgileNotes.AI rolls multiple teams up into an Agile Release Train (ART). Select the ART from the team selector and every view you've seen so far switches into an aggregate, train-wide read — plus two scaled-only views: the Program Board and Dependencies.
In the Demo, three teams — Dragons and Tigers (Scrum) and Juggernauts (Kanban) — belong to a Sample ART. Pick it from the team selector and the app re-scopes to the whole train.
Switching into ART scope
The team selector lists your ARTs alongside your teams. Choosing an ART:
- Re-scopes the Dashboard, Summary, Statistics, and Charts to aggregate every team on the train.
- Unlocks the Program Board and Dependencies views.
- Presents an RTE / Coach perspective — a train-wide read — while each team keeps working in its own team-scoped views exactly as described in the rest of this manual.
Because Scrum teams measure committed-vs-delivered story points while Kanban teams measure flow, the ART views stay framework-aware: they keep the two kinds of delivery side by side rather than adding mismatched numbers together.
Team health
The hard part of running a train is comparing teams that work differently. AgileNotes puts every team — Scrum or Kanban — on one health score from 0–100, so an RTE can see at a glance who needs attention.
The score is framework-aware:
- Scrum teams are scored on projected delivery against the sprint goal, velocity consistency, cycle time, blockers & unplanned work, and epic progress.
- Kanban teams are scored on throughput — the dominant factor, so a team shipping a lot scores well — plus cycle time, a light flow-efficiency signal, and epic progress.
A delivery floor keeps the math honest: a team shipping well above the train’s average can’t be ranked unhealthy just because one secondary signal dips — sustained output is itself a sign of health. Each health card flips over to show the drivers behind its number.
The ART Dashboard
The Dashboard leads with a program snapshot — overall ART Health, Scope Progress (how much committed work is done), and an On Track? projection — followed by a per-team health strip. Below that, the familiar stat row aggregates the train: blockers, risks, bugs, dependencies, and Avg Velocity.
Delivery is split so the two frameworks stay readable: a Done / Forecasted (SP) card for the Scrum teams and a separate Done (SP) · Kanban card, rather than one blended total. Days Since Release reflects the most recent release across any team on the train.
The ART Summary
The Summary opens with the same program snapshot, then assembles an AI-written ART Overview that narrates the increment honestly across frameworks — for example, “Scrum teams committed X of Y points; Kanban teams delivered Z points” — never merging the two. Below it, aggregated blockers, decisions, risks, observations, accomplishments, and sprint goals from every team.
As on a team Summary, the Overview is cached and refreshes at the end of the iteration or when you click Regenerate, and an editable ART Context note lets you add train-level framing for the AI to weave in.
ART Statistics & Charts
Statistics in ART scope shows a team breakdown — each team’s headline metrics side by side, framework-aware — so you can compare delivery and flow across the train in one table.
Charts aggregate trends across every team and iteration of the PI, so a train-wide view rolls the teams up without double-counting the sprints they share.
The Program Board
The Program Board is the classic PI-planning wall, rendered live from your data. Each team is a row and each iteration of the PI is a column, so the whole train’s plan — features, milestones, and the dependencies between teams — is visible in one place.
- Features and epics sit in the iteration where they’re planned to land; an Uncommitted lane holds work that isn’t slotted yet.
- Milestones and significant events can be placed as cards on the board.
- Because it’s generated from the same tickets and sprints the teams work in day to day, the board is never out of date — there’s no separate plan to maintain.
Dependencies
The Dependencies view tracks cross-team dependencies as first-class items: who needs what, from whom, and by when.
- Each dependency records the providing and consuming teams, what’s needed, and a needed-by date.
- Overdue and at-risk dependencies surface in the AI signals and on the Program Board, so a hand-off slipping on one team becomes visible to the teams depending on it — before it becomes a fire.