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).
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. |
Trends & breakdown
- Trend indicators — up arrows mean improving, down arrows declining, a dash means stable.
- Team breakdown — see individual contributions and spot uneven workload distribution.
Tip: as on the Dashboard, click any stat card to flip it and read the full definition plus how it’s calculated.