Invisible Work Risk Index
See which Scrum teams are carrying work that never makes it into tickets, ranked from your existing Jira sprint data.
The work that never reaches a ticket is still real.
Production support, code reviews, ad-hoc requests, the half-hour you spent unblocking another team. The work that does not make it into a tracked item is not less important, but it does not show up on the velocity chart, the burndown, or the predictability scorecard.
The teams carrying the most invisible work tend to look healthy on the surface. Their tickets close, their boards drain, their stakeholders nod. They are also the teams most likely to burn out, miss commitments under load, and absorb risk that no dashboard is signalling.
IWRI surfaces that risk from the data you already have, in your existing Jira Cloud, without asking your teams to log anything new.
Seven indicators, validated across hundreds of teams.
Every indicator went through structured surveys and interviews across teams in banking, telecommunications, and other sectors. The reliability score is the split-half reliability from that validation, exposed in-app so you can see the strength of every signal.
-
01 Production support flow
Reliability 78%How much support work the team handles outside the sprint plan, inferred from comment patterns and rapid-turnaround tickets.
-
02 Code review carry
Reliability 71%Time team members spend on review work that never appears as a tracked item, observed via PR cadence relative to ticket activity.
-
03 Ad-hoc request load
Reliability 66%Volume of micro-tickets created and closed inside the same sprint, a marker for unstructured work hitting the team directly.
-
04 Sprint goal slippage
Reliability 74%Gap between planned and shipped scope across sprints, normalised for team size and sprint length.
-
05 Context switching density
Reliability 86%Average concurrent work-in-progress per engineer, weighted by item type. The strongest single indicator in the validation cohort.
-
06 Documentation drift
Reliability 53%Decay rate of linked Confluence pages relative to ticket activity. Lower bound on the model, but useful as a pattern flag.
-
07 Cross-team helper load
Reliability 68%How often the team is named in other teams' work, surfaced from cross-project linkage.
Four ways to read the score.
-
Risk overview
Every Scrum team in scope ranked into Healthy, Watch, Elevated, and High risk bands, with the indicators that drove each ranking.
-
Flag co-occurrence
Which indicators tend to flag together. Helps you see whether you are looking at one underlying problem or several.
-
Excluded projects
Why a project is or is not in the calculation, with explicit thresholds. No mystery exclusions.
-
Team-versus-team
Compare two teams side by side on every indicator, with a written narrative of where they diverge.
The methodology is in the app, not behind a paywall.
Every indicator's source, validation cohort, and reliability score is documented inside the product. You can read the methodology before you install, while you trial, and after you commit. Nothing about the model is hidden behind a tier.
The recompute cadence is yours to set, the access control is yours to scope, and the data never leaves your Jira Cloud tenancy.