Agile velocity is a historical measure of how much estimated work a team completes during an iteration. When a team uses story points, velocity is commonly expressed as the number of points associated with work completed during a Sprint.
Velocity can support forecasting, but it is easy to misuse. It is most useful as a planning signal for the team that generated the data.
How velocity is calculated
Suppose a team completes 28, 31, 27 and 30 story points during four consecutive Sprints. The simple average is 29 points per Sprint.
If the remaining backlog contains approximately 145 points, a rough forecast might suggest approximately five similar Sprints of work.
That is a forecast rather than a contractual completion date. Future scope, capacity, uncertainty and dependencies can alter the result.
Why historical velocity matters
Forecasts based entirely on initial estimates can create false precision. Velocity introduces actual delivery history into the planning process.
Velocity is not a productivity score
Management should be cautious about using velocity to rank teams or establish performance targets.
If teams are rewarded for increasing points, the estimation scale itself can inflate without any corresponding increase in delivered value.
Velocity and schedule forecasting
A program planner can use Agile delivery trends as one input to forecasting, particularly when a major capability depends on completing a known backlog.
Velocity does not automatically account for external dependencies. Software may appear likely to finish on time while a test environment, interface delivery or certification activity controls the actual program milestone.
Those dependencies belong in the program-level schedule.
Velocity and uncertainty
Velocity varies from Sprint to Sprint. A stronger forecast considers a range of historical outcomes rather than relying only on one average.
This is conceptually similar to uncertainty analysis used in schedule risk analysis: a range of plausible outcomes can provide more decision-useful information than one deterministic date.
Velocity becomes meaningful only when the definition of completed work remains consistent. Continue with Definition of Done vs Acceptance Criteria.