How else to measure team performance other than velocity?

[Chimena Ijeh]

I will like to calculate team cycle and lead times. What tool in JIRA would be able to provide me with this data. I have checked the Reports Feature, but it does not have anything for cycle time.

[Mariana_Pryshliak_SaaSJet]

Hi @Chimena Ijeh 

It's easy to resolve with using the Control Chart, Time in Status for Jira Cloud, or Time between Statuses.

Control Chart provides shortened information (average time) and only in charts, but it can be helpful for you.

Time in Status for Jira Cloud generates a report of how long issues have been staying in a specific status. Concerning your issue - you get the Cycle and Lead Time data by grouping time in statuses. Go to the Status Groups and here you can add New Group or manage existing ones (edit or delete).

Also, you can try Time between Statuses, which gives the ability to monitor how long it takes to move from one status to another.

Just a few clicks and you will get all the necessary data.

I hope you'll find this info helpful

[Emre Toptancı _OBSS_]

Hello @Chimena Ijeh ,

If you are interested in a ready built solution, our team at OBSS built Timepiece - Time in Status for Jira app for this exact 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. The app can calculate averages and sums of those durations grouped by issue fields you select. (For example see the average "Cycle Time" per component and issuetype or see the sum of "Waiting for Customer" time project). 

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

EmreT

[Benjamin]

Hi @Chimena Ijeh -

There's various reports that can help that is out of the box. The velocity report is to help with understanding what the team can handle after analyzing the commitment and completed story points of the previous sprint. 

If you looking for Issue cycle times, use the control chart. display outliers, how's the team averaging and how wide is their deviation. Very useful in both Kanban and scrum. 

[Chimena Ijeh]

Thank you for your response.

There is no control chart in Reports section of the JIRA tool. Could this be as a result of the version? I am using Next-gen project.

Otherwise, how can I get the control charts feature enabled?

What other out of the box reports out there that can help?

[Benjamin]

HI @Chimena Ijeh 

Next-gen is a new feature out of the box. Quick setup with certain limits compare to classic project. Like what you have observe, which is limited report set. 

If you are focus on reporting and want to have full feature capabilities, would move to classic project so you can get all the reports available in Jira software.

Hope this helps.