In Jira, every issue belongs to one team at a time. There is a Team field, and that is the top of the structure — there is nothing native above it.

But planning rarely happens at the team level. In a PI planning session the question in the room is about the group: what has this Agile Release Train (ART) committed to, together, across all its teams — plus the work still sitting at ART level waiting to be broken down?

The missing tiers

Most scaled organisations have at least two levels above the team:

  • The ART (or programme, or tribe): a long-lived group of teams delivering together.
  • The value stream (or portfolio, or line of business): a group of ARTs aligned to a business outcome.

These groupings drive funding, planning and reporting. Yet in the work tracker they often exist only as naming conventions, labels or tribal knowledge.

What happens instead

Because the tracker can't see "this ART," someone rebuilds the picture by hand every planning cycle:

  1. Export each team's committed work.
  2. Find the work that sits above the teams and hasn't been assigned yet.
  3. Group everything in a spreadsheet using their own knowledge of who belongs where.
  4. Total it up and compare it with the group's capacity.

The result is usually accurate for about a day. As soon as teams start delivering and refining, the spreadsheet drifts from reality.

Making group-level planning sustainable

A few practices reduce the manual effort and the drift:

  • Make group membership explicit and maintained. Record which teams belong to which ART and value stream somewhere authoritative, and keep it current as teams change.
  • Include unassigned work. Group-level commitments include work that hasn't yet been broken down to a team. Leaving it out understates the load.
  • Roll up from live data. Wherever possible, compute group totals from the tracker rather than from a copied snapshot.
  • Compare against group capacity, not team velocity alone. A group's ability to absorb work depends on all its teams together.

The two missing tiers aren't complicated. They just need to exist somewhere more durable than a planning-week spreadsheet.

Tags: #SAFe #AgileReleaseTrain #PortfolioPlanning