iskue

Features · Scaled agile

Scaled agile, without the second tool

Agile Release Trains, Program Increments, a program board with dependency arrows, value streams with lean-budget guardrails — on the same tickets.

Enterprise edition

Included in Enterprise.

When several teams ship one product, the questions change: what did the train commit to this increment, which dependency is about to slip, is the value stream inside its budget? The scaled-agile suite answers them from the tickets your teams already use. Teams group into Agile Release Trains, trains into solution trains; each PI carries objectives, risks, milestones and a burn-up; a program board lays work out by team and iteration with dependencies drawn between cards; and persona rooms give the RTE, the team and the portfolio each a front page of their own.

1–8 iterations + IP per PIROAM: 4 risk statesBusiness value 1–103 persona rooms

What you get

  • Trains and solution trains — Teams belong to an ART, ARTs to a solution train; the solution-train report lists each train's team count and current PI at a glance.
  • Program Increments with a cadence — A PI is future, active or done. Generate its cadence in one step: one to eight development iterations of 7–28 days, then an Innovation & Planning iteration, with the PI end date snapping to the last day.
  • Objectives with business value — Team or ART-level objectives, committed or stretch, each with planned business value 1–10 and actual value 0–10 scored at the end.
  • Predictability, computed — The PI's predictability measure is actual over planned business value across committed objectives — an unscored committed objective counts as zero, so the number is honest.
  • ROAM risks and milestones — Risks carry an owner, an optional linked ticket and a ROAM state — resolved, owned, accepted, mitigated; milestones have a name and a date and pin to the top of the program board.
  • The program board — Iterations as columns, teams as rows; drag cards into any cell. BLOCKS links are drawn as arrows and turn red when the blocker is scheduled after the work it blocks.
  • ART dashboard — Predictability trend across PIs, the current burn-up of scope versus accepted points, per-team completeness by count and points, open cross-team dependencies, and an Inspect & Adapt summary exported as Markdown.
  • Value streams and lean budgets — Each value stream owns strategic themes and a budget in points with a warning threshold (80% by default); guardrails report committed and done points, utilisation and OK / WARN / OVER status per stream.

See it — the program board

PI 2026.4Iter. 1Iter. 2Iter. 3Iter. 4Iter. 5IPMilestonesPSD2 audit · 14 MarPaymentsPlatformMobileDataPAY-212FEAT3-D Secure v2PAY-230FEATRefund APIPLT-88ENABToken vaultPLT-91ENABRate limiter v2MOB-57STORYWallet checkoutMOB-61STORYReceipt shareDAT-19STORYSettlement feedDAT-24STORYChargeback ETL
Program board. Drag a card to any team × iteration cell; BLOCKS links are drawn as arrows and turn red when the blocker lands in a later iteration than the work it blocks. Milestones pin to the top row.

A hierarchy that is enforced, not implied

Projects that adopt the scaled hierarchy get levelled ticket types: Portfolio Epic above Capability above Feature above Story, with the ordinary Epic slotted in as well. The parent link on a ticket is only accepted when the parent's type sits strictly higher, validated on the server — so a story cannot parent a feature by accident, and the roll-up from portfolio epic to story always reads in one direction.

Rooms: one front page per persona

Three rooms, remembered per browser. The RTE room opens on the ART report and the solution trains — current PI, dependency health, predictability. The team room shows the team catalogue and your own open work. The portfolio room shows budget guardrails, which goals serve which strategic themes, and cross-project progress. The same data, arranged for the person looking at it.

Portfolio: every project on one screen

The portfolio page lists every project you can see as a row, with its tickets spread across status-category columns, filterable by strategic theme and annotated with the value-stream guardrails — so the question "how is the Payments stream doing against its budget" has a page, not a spreadsheet. Strategic themes themselves are a shared catalogue: any ticket can carry one, and TQL queries by theme and PI like any other field.

In practice

POST /api/v1/pis/{id}/generate   { "iterations": 5, "iterationDays": 14 }
GET  /api/v1/pis/{id}/predictability
GET  /api/v1/pis/{id}/board
GET  /api/v1/arts/{id}/report
GET  /api/v1/value-streams/guardrails

TQL: pi = "PI 2026.4" AND team = Payments AND statusCategory != DONE

See Iskue on your own screen

A demo takes half an hour. A pilot runs on your servers, with your data, from day one.

Request a demoRead the FAQ