Sprint Insights
Insights is the reporting page for sprints: how the current one is going, how past ones went, and where the workload actually sits. Pick a sprint at the top and the page reads on it.
The sprint at a glance
The KPI bar summarises the selected sprint:
| Figure | What it tells you |
|---|---|
| Total tickets | The sprint's size |
| Completed | How much of it is done |
| Created this sprint | Tickets born mid-sprint |
| Scope added after start | Work added after the sprint began — the scope-creep number |
| Hours logged | Time actually recorded against the sprint |
The one to watch is scope added after start. A sprint that keeps growing after day one isn't failing at delivery — it's failing at planning, and this number is where that becomes visible instead of arguable.
Velocity
The velocity chart shows completion across sprints, so you can see whether your team's throughput is steady, growing, or was flattered by one heroic fortnight. Velocity is the number that makes the next sprint plannable: commit to roughly what you actually complete, not what you hope.
Breakdown and team workload
- By status / by priority — the shape of the sprint's tickets: how much is still To Do, how much of it is Critical.
- Team workload — per member: their tickets, completed count, hours logged, and a rating. Use it to spot imbalance early — one person carrying the sprint is a risk, not a compliment.
- Epic progress — how far each initiative in the sprint has come, which is often the version leadership actually wants.
Reading it honestly
Insights reports what people entered. If time isn't logged, hours are fiction; if tickets aren't moved to done as they finish, completion lags reality. The fix for ugly numbers is sometimes the team — and sometimes just the hygiene in Estimates and logging time.