Generating data for Kanban

Question

How do I generate a graphical data for throughput and cycle time In Kanban?

Is there any way to map it on Jira and confluence. Recommended plugins for both. Or if you can do it without plugins?

Is there an automatic way to do this, where you don’t have to manually put the data in to get the results?

Danut M _StonikByte_ · Answer

Hi @semer Mahmoud

Try our Great Gadgets app for Jira. It offers all the gadgets needed for calculating and displaying the throughput (Kanban velocity) and cycle/lead time (as trend chart or control chart) on Jira dashboards. The gadgets have also a Data tab that you can use to see data for individual issues.

In case of questions, please don't hesitate to contact us at support@stonikbyte.com.

Danut.

semer Mahmoud · Answer

Thank you EmreT, I will definitely look into this.

Emre Toptancı [OBSS] · Answer

Hello @semer Mahmoud ,

The out of the box solution included in Jira Software for Cycle Time, Lead Time and similar metrics would be the Control Chart among Kanban Board Reports. It has limited customization options but might do the trick.

For throughput you can run JQL queries like...

project = ABC and status CHANGED FROM "In Progress" TO "Resolved" AFTER "2020-07-01 00:00" BEFORE 2020-07-31 23:59

This query will return the issue that were transitioned from InProgress to Resolved between the given dates. You can customize this according to your needs.

As an alternative that gives more control over reporting, our team at OBSS built Timepiece - Time in Status for Jira app for this need. It is available for Jira Server, Cloud and Data Center.

Time in Status allows you to see how much time each issue spent on each status or assigned to each assignee or group. You can combine statuses into consolidated columns to see metrics like Age, Cycle Time or Lead Time. All durations can be displayed in various formats including days, hours, minutes even seconds.

One important feature is History Trimming. Time in Status allows you to set a date range for the report and only parts of issue histories that are between the given dates are included in the report. If some or all of your issues follow a repeating workflow, set those dates to your liking, the report will simply ignore what happened earlier or after.

The app can calculate averages and sums of those durations grouped by issue fields you select. (For example see the average InProgress time per project and per issuetype OR see the sum of InProgress time per component).

The app has custom calendar support so you can get your reports based on a 24/7 calendar or your custom business calendar. (This one is important because a 24/7 calendar in most cases shows misleading data. For example an issue created at 16:00 on Friday and was resolved at 09:00 on next Monday seems to stay open for 2,5 days but in terms of business hours, it is only a few hours. You can see this using Time in Status by OBSS.)

Using Time in Status you can:

* See how much time each issue spent on each status, assignee, user group and also see dates of status transitions. Get metrics like Lead Time or Cycle Time.
* Calculate averages and sums of those durations grouped by issue fields you select. (For example see average InProgress time per project and per issuetype.)
* Export your data as XLS, XLSX or CSV.
* Access data via REST API.
* See Time in Status data and charts for each issue as a tab on issue view screen.

Timepiece - Time in Status for Jira

Charts and graphs are currently limited to a single issue (on issue view screen). More is coming soon.

EmreT