Kanban velocity report

Examples

This example shows how to build a velocity chart for one or multiple Kanban boards. We utilize a velocity chart gadget to create these charts on the Jira Dashboard.

There is no built-in Kanban velocity gadget in Jira - therefore, this example utilizes the functionality of apps by Broken Build:

Use cases

Track velocity for one Kanban team (one Kanban board)

Kanban velocity report for one team

The chart is simple; it shows:

  • “Completed work” metric in Story Points for the “bi-weekly” time interval.
  • “2-intervals” moving average (the dashed line)

The main settings to specify are:

  • #1 - choose Kanban board
  • #2 - choose “Estimation field,” which can be Story Points, issue count, time estimates, or any Jira numeric field
  • #3 - choose the reporting period
  • #4 - choose how you want to group time intervals (e.g., weekly, bi-weekly, monthly, etc.)
Main settings to configure Kanban velocity gadget

Track velocity for multiple Kanban teams (multiple Kanban boards)

The data on the chart is the same with the valuable addition of breakdown by Kanban boards:

Multiple Kanban teams on the same velocity chart

Adapt to unique processes of different teams with “custom done statuses” settings:

Custom done statuses to adapt to specific team processes

Use breakdowns for deep analysis

Breakdowns by issue types and priority

You can use any Jira field to break down completed work for deeper analysis. The chart, for example, shows a breakdown by issue types and priorities.

Other practical examples of breakdowns are by people (“Assignee” field), components, labels, releases, etc.

Filter by anything

Play with the chart by filtering the data by any breakdown. Below, you can see the filtered chart and work items of completed stories by Bill:

The report data filtered by stories completed by Bill

Or create charts already filtered by any Jira field or JQL:

Settings to create velocity chart filtered by Jira fields or JQL

Set expectations (or even KPIs) with target lines

Let’s say your team (or set of teams) must complete at least 20 issues per time interval. Use target lines to visualize such expectations or KPIs:

Target line for the expected minimum completion rate

Build your own reports

How to find Kanban velocity report for Jira Dashboard

In the list of gadgets for Jira Dashboard, find “Cross-team velocity chart for Kanban boards” gadgets (#1 on the chart) in case you’ve installed the Velocity Charts app, or in case of the Agile Reports app, follow #2 on the chart:

Spot Broken Build's gadget on your Jira Dashboard

Apps used in this example

Use our examples to build your use cases on the Jira Dashboard with these apps:

Both apps used in these examples have a 30-day free trial and are completely free for teams under 10 people.