Velocity chart (Kanban)


Velocity in Kanban:
It is beneficial for Kanban teams to have a notion of delivery cycle and velocity, at least from reporting & analytical points of view.

Velocity is the average amount of work a team can complete in a delivery cycle. A delivery cycle is a constant period of time like a week, two weeks, or a month.

By knowing their velocity, a team can predict how much work they are able to deliver in the future. And predictability is the primary outcome of our efforts regarding process setup.

Concerning Kanban, the notion of derived velocity is often used. It is calculated by multiplying the throughput by an average story size.

But wouldn’t it be great to have actual data about a team’s velocity? In our humble opinion, such data is much more actionable than the derived velocity.


Kanban Team Velocity Chart shows the amount of work completed in each delivery cycle. It helps to answer the following questions:

  • Is the team’s flow stable or erratic? Therefore, is the team’s performance predictable or not?

  • What is the productivity trend for the team?

Velocity chart for Kanban

Chart analysis

Let’s analyze the chart above. This burnup chart is built for team “Theta,” which follows the Kanban process. The team follows a weekly delivery cycle.

The chart shows the velocity data for the past five weeks. The green line is the average line calculated as the moving average of two previous intervals. Here is how data points of this average line are calculated:

Start date of the delivery cycle

Velocity (in story points)

Moving average

Calculation formula

Start date of the delivery cycle

Velocity (in story points)

Moving average

Calculation formula




there are no two delivery cycles to calculate the moving average












=(16+23)/2 (which, actually, is equal to 19.5, but we round it to 20)





The velocity significantly fluctuates from sprint to sprint, but the moving average value is stable at around 20 story points. Thus, we conclude that team Theta’s performance is predictable.

Chart configuration

Please, continue to article.