What is Sprint Velocity?

Sprint velocity is the amount of work a team completes per sprint and aids capacity planning and forecasting. Tracked over several sprints, it gives a realistic basis for committing to future work. Comparing velocity across teams is meaningless because point estimation is relative to each team. For context, use the rolling average of recent sprints as the planning baseline; there is no cross-team benchmark, only a team's own trend. Treat an external benchmark as a reference point rather than a universal target: company stage, sector, customer mix, pricing model and measurement definitions can materially change what “good” looks like. Read Sprint Velocity alongside Cycle Time and Throughput; together these measures provide a more balanced view and reduce the risk of optimizing one number at the expense of the wider outcome.

Define every included record and value consistently, and reconcile the total to its source system before comparing periods. Use stable production boundaries and timestamp definitions, and distinguish planned work from incidents, rollbacks and failed deployments. Measure at service or team level and keep the start event, end event and production boundary stable; portfolio averages can hide a fragile component. A dashboard should show the current value, prior-period comparison and a trend rather than presenting one isolated reading.

Treat the metric as a prompt for system improvement: reduce batch size, automate safe delivery, strengthen observability, rehearse recovery and use blameless reviews to eliminate recurring failure modes. Common pitfalls: comparing velocity across teams. Record the definition beside the dashboard, review it when systems or processes change, and annotate unusual events so future readers can distinguish a genuine performance shift from a data or timing effect.