There is a workaround in Atlassian’s own project manager guide to Jira Align. The five health dimensions — budget, people, quality, risk and schedule — are set by hand with a typed reason, and the product keeps no history of them, so the guide notes that it “really is a point in time view” and that practitioners type the date into the reason field to compensate (part three of the guide).
Read that again as a governance artifact. The record of what the program office believed about a program, and when, is a string somebody remembered to start with a date.
We are unusually well placed to be annoyed by this, because Jira Align also holds the single best idea in portfolio management, and we rebuilt it.
The dependency as a contract
In Align, a dependency is not a line on a diagram. The requesting team proposes it and the responding team accepts or counter-proposes; only when both have agreed does the connector on the wheel map change (the flow, documented). Somebody at Atlassian understood that a dependency nobody agreed to is a wish, and that is the correct insight — it is the same insight this product’s whole doctrine runs on, arrived at from the other direction.
So our dependency register is that shape natively: requested by one initiative, accepted by a person answering for the other, both signatures stamped by the database from the session. A request nobody has answered is shown, counted, and held outside every dependency figure on the page, because a contract with one signature is a proposal. We skipped the wheel map. A red edge turning blue is decoration on top of a fact that is already legible in words.
The difference between the two products is what happens to that fact afterward. In Align, the health of the thing the dependency governs is a point-in-time color. Here, every acceptance lands in an append-only trail — one that refuses deletion for owners and for the database superuser, which we know because we tried the delete rather than reading the manual.
What Align is genuinely good at
Weighted shortest job first is native on feature, capability and epic backlogs, and exportable (the knowledge base article). Financials track forecasted, estimated and accepted spend against a portfolio funding plan, with blended rates or per-person cost centers (the community article). Risk is ROAM-native. For an organization running the Scaled Agile Framework at real scale — release trains, program increment planning, a room of two hundred people and a wall of dependencies — Align is the instrument built for that ceremony, and this product is not.
Two things are worth knowing before that becomes the plan. Capacity in Align is team-level only, in story points or member-weeks, with no named-person allocation and no booking model (the team load widget, documented) — so a portfolio office asking who is overloaded next month is asking a question the product does not model. And the price is public enough to plan around: the Strategy Collection is listed at $77,400 a year for one to fifty full users, with integrated Jira users free.
The direction of travel
Align has no native generally available generative AI. The concrete artifact is a read-and-summarize Rovo skill in an early access program. Meanwhile Atlassian announced Focus, a new enterprise strategic portfolio offering, which is a reasonable thing for a large vendor to do and a fact a buyer should hold in view when signing a multi-year Align agreement. A defect on the ROAM report has sat in Gathering Interest since 2023.
The counter-argument
The strongest objection to everything above is that we are comparing products built for different organizations. Align instruments the Scaled Agile Framework: trains, increments, ceremonies, a program office that runs a cadence. We instrument a delivery organization that is getting smaller and more machine-produced. Both are true.
The reason it still matters is that the ceremony is the thing under pressure. Gartner expects 60% of organizations to run smaller software engineering teams at scale by 2029, from 15% in 2026; BCG Platinion describes software factories where as few as three engineers run delivery and humans no longer write code — and, in the same piece, that every stage gate has a human accountable for approval. A three-engineer pod does not hold a program increment planning event. The dependency contract survives that transition intact. The two-hundred-person room does not, and neither does a health color somebody has to remember to set.
Forrester’s portfolio practice reads the same way: strategic portfolio management is now “one of the most critical capabilities” for enterprises under constant disruption. The layer above delivery gets heavier while the layer below it gets thinner, and the record it keeps has to survive being asked about a year later.
Choose Jira Align if…
Choose Jira Align if you are running the Scaled Agile Framework at scale and intend to keep running it. Program increment planning, the dependency wheel in a room, weighted shortest job first on a real backlog, and a portfolio object that maps cleanly onto trains and epics — Align is built for that operating model, this product is not, and no amount of evidence discipline substitutes for a tool that matches the ceremony you actually run.
Choose it also if your Jira estate is large and your users are already licensed. Integrated Jira users are free on Align, which changes the arithmetic considerably.
Come here instead if the question that keeps arriving is historical: what did we tell the steering committee in March, was it still true in April, and who signed. That is the question a point-in-time health view cannot answer, and it is the one this register was built around.