What it is
Track View sits under the sprint summary and shows sprint progress as racers moving along a track between a start line and a finish line. It's not a burn-down chart — think of racers on a track, not lines on a graph. There are three kinds of marker:
- The team actual marker — how much of the committed work is done (the same figure the summary's progress reads).
- The team expected marker — how far through the sprint you are by elapsed time. On pace, actual and expected sit together.
- A per-person marker for each teammate — where each person is against their own effective capacity (their available time, adjusted for how much of it is committed to this team), not just the work assigned to them. Someone under-loaded finishes short of the line with room to help; someone over-loaded is pushed past it.
Reading the finish line: does the plan fit?
The track now deforms to show committed workload against the team's capacity (bandwidth), so you can see at a glance whether the sprint was even winnable:
- A balanced sprint (committed work ≈ capacity) shows one finish line at the end of a full solid track — the familiar look.
- An overloaded sprint (committed work > capacity) keeps the solid track running to the end but slides the capacity finish line inward, leaving a colored over-capacity stretch between it and a second workload finish line at the far end. The team has to run past its capacity line to finish everything — a plan carrying more than it can sustainably deliver.
- An underused sprint (committed work < capacity) stops the solid line short at the workload finish, with the rest of the track drawn as a dashed remainder — spare capacity the plan didn't use.
This solid-vs-dashed language is about race distance (how much work there is to run) and is distinct from the solid/dashed capacity bar on the summary band, which breaks a single person-or-team capacity figure into available vs unavailable time — see Capacity & Availability.
Reading the race: ahead or behind?
The gap between the team actual and expected markers sets the sprint's progress state, shown by color: Exceeding, Ahead, On Track, Behind, Lagging, or Critical, from best to worst. A small gap either way is normal — On Track and Ahead cover most healthy sprints. A large gap toward Behind, Lagging, or Critical means actual progress has fallen well short of where the timeline says it should be.
Because the expected marker always runs the full schedule track, an underused sprint that finishes all its (light) workload can show the actual marker resting at the short solid line while expected marches on — that's the "you had capacity to spare" signal, not a failure.
What to do about it
Check Track View mid-sprint, not just at the end. If the capacity finish line is pulled well inside the workload finish, the sprint was overloaded from the start — rebalance scope or availability rather than trying to out-run it. Catching a Behind or Lagging race state early leaves time to react; Critical late in a sprint is largely a lagging indicator. Pair it with Momentum: a sprint that's both Overdrive and Lagging is under load pressure and behind on execution at once — a stronger signal to intervene than either alone.