Loading
Because the moment it is reported upward as a performance figure, estimates inflate to meet it. The number keeps rising and stops describing anything real.
Velocity is the estimated size of work a team actually completed per sprint, averaged over recent sprints.
It computes from completed tasks and their estimates — no separate entry. It is shown per team over time, with the spread rather than a single flattering average.
A team averaging sixty points over five sprints, with a range of fifty to seventy, can be told honestly that fifty is a safe commitment and seventy is optimistic.
It will not compare teams. Estimates are calibrated within a team and mean nothing across them; Loop does not present cross-team velocity because the comparison is misleading.
It informs sprint planning and the roadmap's confidence, and nothing else. It is deliberately absent from anything a person is appraised on.
It is available for forecasting. Using it as a target is what breaks it.
It counts in the sprint it completes in, not proportionally.
The last five by default, with the range shown.
Fourteen days, every module, no card. Or half an hour with someone who will run it on your own records and tell you where it does not help.