Statistics
The Statistics view lays out detailed metrics and trends for the team. Use the scope toggle to look at just the current sprint/iteration or the whole PI.
Scope toggle
- Scrum: Sprint View (current sprint) vs PI View (aggregated across the PI).
- Kanban: Iteration View (current flow window) vs PI View (across all iterations in the PI).
On an ART, Statistics shows a framework-aware per-team breakdown across the whole train — see Scaling with ARTs.
Key metrics & how they’re defined
Every tile here matches a definition the app shows when you flip the card. The most important:
| Metric | Definition |
|---|---|
| Velocity | Sum of story points across every ticket that reached Done in this sprint. |
| Avg Velocity | Mean velocity across the team's 5 most recent non-IP sprints, excluding the current one. |
| Predictability | Delivered SP ÷ Forecasted SP × 100. Forecasted = points committed at sprint start (Scrum). |
| Throughput | Count of tickets that reached Done during the sprint or iteration. Releases, KT, and support tickets are excluded. |
| Cycle Time | Per ticket: working days from the start of Dev onward — Dev, Code Review, QA Ready, QA, and Merge — plus prior-sprint rollover. UAT is excluded (outside the team's control). Averaged across tickets with at least one counted day. |
| Lead Time | Per ticket: waiting days + cycle-time days + rollover. Averaged across tickets with a cycle time. |
| Flow Efficiency | Active days (Dev / CR / QA / UAT / Done) ÷ total in-flight days × 100. |
| WIP | For each working day, count tickets in Dev, Code Review, or QA; sum across days ÷ working days. |
On a Kanban team
A Kanban team (like Juggernauts) gets a flow-oriented version of the same view. Instead of velocity and predictability, the headline metrics are Throughput, Cycle Time, Lead Time, Flow Efficiency, and WIP, with the scope toggle reading Iteration vs PI.
| Metric | Definition |
|---|---|
| Throughput | Count of tickets that reached Done in the iteration. |
| Lead Time | Per ticket: the wait in Ready plus cycle time — total time in the system. |
| Flow Efficiency | Active days ÷ total in-flight days × 100 — how much of the time was spent working vs. queued. |
| Avg Age / Aging > SLE | How old in-flight work is, and how much of it has exceeded the team's Service Level Expectation. |
Trends & breakdown
- Team breakdown — see individual contributions and spot uneven workload distribution.
- Sprint Comparison links — in the comparison table, any sprint whose header is a link has a generated Sprint Report — click it to open that report in a new tab. Sprints without one stay plain text.
Tip: as on the Dashboard, click any stat card to flip it and read the full definition plus how it’s calculated.