How to derive the kanban metrics in Jira

[Pavan]

Hi,

I had a request to generate the following metrics from Jira Kanban board

1. Throughput

2. Lead Time

3. Cycle Time

Any ideas?

Thanks,

Pavan

[Warren]

Hi @Pavan 

I'm assuming that you're thinking about using the REST API for this, because I can't see any other way of doing it.

Using the REST API documentation you will need to create a CFD and build up some of the stats from that. 

[Pavan]

Could you please elaborate?

[Warren]

You may want to look at a book like Daniel Vacanti - Actionable Agile Metrics for Predictability, which gives a great description of using a CFD to get these metrics.

I build up a CFD by getting the project stats every morning - how many items in each column of the board, using the Jira API.

Average throughput is then the number of closed items today minus closed items at some previous point, divided by number of days.

For cycle time, you need to look at all tickets closed in your period. For each ticket, the API can give you the history, where you find the date work started on it and the date it finished. The difference between these dates is cycle time, find the average of all tickets.

According to Daniel Vacanti, Lead time and Cycle time are pretty much the same thing, but you get the idea.

[Mark Kern [SaaSJet]]

Hi @Pavan 

Or you can try to solve this request by using an application like these::

Time in Status for Jira Cloud by SaaSJet - will help you monitor the Cycle and Lead Time by grouping statuses and can show this data as charts. 

Time Between Statuses - calculate the Cycle and Lead Time of your Jira issues by setting start/stop/pause statuses

Hope it will be useful for you.

Regards

[Mark Kern [SaaSJet]]

Also, you can try buld-in Control Chart

[Emre Toptancı _OBSS_]

Hello @Pavan  ,

Our team at OBSS created Time in Status app for your time related needs. It is available for Jira Cloud, Server and Data Center.

Using Time in Status you can report how much time each issue spent on each status, each assignee or even each user group. (useful for calculating lead/cycle times and identifying bottlenecks in your process). You can also see the number of times each status or transition was used (very useful for inspecting things like reopen counts). You can also list the status entry/exit dates.

You can get sums or averages of issues, grouped by any issue field(s) you like.

Even better than Jira Control Charts, you can produce reports based on the default 24/7 calendar or define your own business calendars with custom workdays and working hours. 

All data can be exported as XLS, XLSX, CSV.

Emre Toptancı

OBSS

Edit on 30 Dec 2019: We recently introduced Consolidated Columns (which display the total duration for a group of statuses) so users now can create columns for metrics like Cycle Time or Lead Time and pick which status durations to include in these columns.