How many tabs do you need to open to know how a sprint is doing? The Sprint Health Score pulls all your active modules together into a single number from 0 to 100 — the first thing a PO or RTE sees when opening the team dashboard. No tour past every module before the standup. Just one number, and you know whether there is something to talk about.
3.9 · 30%
3.8 · 25%
3.6 · 25%
4/6 · 20%
The Sprint Health Score is a composite number from 0 to 100 that reflects the status of a running sprint, calculated from the data of your active modules. It is not a KPI and not an assessment tool — it is an early-warning signal for the team and for everyone coaching the team.
The score combines four components, each with its own weight:
Each component is normalised to a 0–100 scale and counts towards the weighted total. The weighting is transparent: the scoreboard shows the raw value, the normalised score and the weight for every component. No black box.
The score is automatically available as soon as at least one module provides data for the running sprint — no configuration needed. If a module has no data (yet), that component simply doesn’t count: the weights of the remaining components are redistributed proportionally. That keeps the score honest about the data that is there, and it becomes more complete as you use more modules.
The final score gets a label and a colour, so you know where you stand in half a second:
No data in the sprint yet? Then Iterr honestly shows ‘No data yet’ instead of a misleading number.
For RTEs coaching multiple teams through the Groups module, the Sprint Health Score is visible per team in a single overview — without opening each team separately.
The Sprint Health Score is primarily built for POs, RTEs and agile coaches who want to quickly oversee the status of one or more teams — without opening every individual module. And for the team itself, the score is a shared reference point: one number to talk about, instead of four separate dashboards.
