Sprints and agile · Autessa Vision
Sprint progress and velocity
Autessa Vision measures every sprint as it runs: completion by story points (or by task count when nothing is estimated), a pace check that compares progress with how much of the sprint has elapsed, a countdown to the end date, and To Do, In Progress and Done counts. When a sprint closes, its done points become its velocity.
The problem
You find out a sprint failed on its last day
Burndown charts are only useful if someone checks them. Vision puts the signal in the sprint header everyone already looks at, and calls out “behind pace” when progress trails the calendar by more than 10%, while there is still time to adjust scope.
What you get
- Progress is by story points when tasks are estimated, otherwise by task count.
- Pace compares progress with elapsed time; a sprint is behind when progress trails elapsed time by more than 10%.
- A countdown shows days left until the end date.
- Status pills show how many tasks are To Do, In Progress and Done.
- Completed sprints show their velocity: points completed out of points committed.
- Inside a sprint, finished tasks move to a Completed timeline grouped by the day they were done (Today, Yesterday, then dates).
- Recent velocity becomes the default capacity on the Triage page.
How it works
How does sprint progress and velocity work in Autessa Vision?
Estimate
Give tasks an estimate in points on the task page, in bulk on the Triage page, or let Vision AI suggest one.
Run the sprint
As tasks reach the done column, the sprint header updates progress, pace and status counts.
Read the signal
If the header says behind pace, move scope out with drag and drop or ask the Sprint agent what is at risk.
Close and record
Completing the sprint records its velocity, which feeds the next sprint’s capacity.
Every option
Sprint measures
| Option | What it does |
|---|---|
| Progress | Points done ÷ points committed, or tasks done ÷ tasks when unestimated. |
| Pace | Progress versus the share of the sprint’s calendar elapsed; behind when trailing by more than 10%. Active sprints only. |
| Countdown | Days until the end date. |
| Status counts | To Do, In Progress and Done, mapped from your columns. |
| Velocity | For a completed sprint: points completed of points committed. |
| Completed timeline | Done tasks grouped by the day they finished, most recent first. |
Permissions
Who can do what?
| Role | Can |
|---|---|
| Anyone who can see the board | See progress, pace, countdown and velocity. |
| Team member | Change estimates and move work that drives the numbers. |
AI assist
How Vision AI helps
The Sprint agent reads the active sprint and answers in plain language: how it is tracking, what is at risk, and who is overloaded. Pulse also includes sprint progress in its daily digest.
Vision AI always shows a preview or asks first. You decide what is applied.
Meet the Vision AI agents →FAQ
Questions about sprint progress and velocity
Does Vision track sprint velocity?
Yes. Each completed sprint shows points completed out of points committed, and recent velocity becomes the default capacity on the Triage page.
How does Vision decide a sprint is behind?
It compares the share of work done with the share of the sprint’s calendar that has passed. If progress trails by more than 10%, the sprint shows as behind pace.
What if we do not estimate in points?
Progress falls back to task count, so the measure still works without estimates.
100% customizable, code and all
Make Autessa Vision fully your own.
Use it out of the box, then change anything. Ask Autobot, Autessa’s AI builder, for a new field, screen, report, workflow or agent and it builds it into your copy of the app. Or open the code and edit it yourself. Nothing is locked: the app, its data and its code are yours.
Start free and make it yours