Velocity and throughput

Velocity tracks the amount of work that can be completed on average in story points per sprint.^[1] For example, a team might complete 30 story points in Sprint 1, 25 in Sprint 2, and 35 in Sprint 3, averaging 30 points per sprint. Teams use this average for sprint planning and release forecasting.

Throughput measures completed work items regardless of size. A team might complete 8 user stories in week one, 6 bugs in week two, and 7 features in week three. Unlike velocity, throughput counting treats all items equally, making it useful for spotting workflow blockages.

Consider a mobile app team that maintains a velocity of 40 points per sprint but only completes 5 items. Another team does 25 points but completes 12 items. This comparison helps identify if the team is taking on too many large items or needs to break down work differently.