Tracking Team Performance in Jira

[zoeyreynolds]

I'm looking to monitor my team's monthly performance. They create tasks daily in Jira and mark them as complete upon finishing. What's the most effective method for assessing our overall business progress and identifying top-performing staff members?

[Valeriia_Havrylenko_SaaSJet]

Hi @zoeyreynolds 👋

As stated earlier the most frequently used metrics are Cycle Time and Lead Time.

I hope you like pizza, so here’s an example of how to distinguish Cycle and Lead time:

Also you can read an article 3 tools to analyze Cycle and Lead Time in the Jira 

And here i have 2 add-ons for you

• Time in Status for Jira by SaaSJet help you to get the Cycle and Lead Time by grouping time in statuses. 

Also plugin generates 7 types of time reports To analyze the report up close with all the intrinsic data, you can export it as XLS or CSV files. Also, you can view all reports as charts (Pie, Bar and Area Charts) and export them too. 

• Another option will be Time Between Statuses by SaaSJet to calculate the status to status time. This app allows you to set the start/stop/pause timer preferences and highlight overdue issues by setting time limits.

You will also see results on a ticket by Issue View Panel, workflow, average, and on a graphic histogram 🔽

Add-ons have a 30-day free trial version and free up to 10 users. 
Please, let me know if you have any questions

Hope it helps 😌

[Amay Purohit_RVS]

Hi @zoeyreynolds 

Welcome to the Atlassian community !!

You can calculate the total time taken by each issue assignee to measure the performance of the team members. We have built an app for the same use case.

Time in Status Reports 

You can track the time taken in each status for the issues with multiple types of reports, graphs , gadgets, status grouping and lot more. You can easily group your statuses via our app and find out the total resolution time for each ticket by each assignee.

Disclaimer : I work for RVS, the vendor for this app

[Gizem Gökçe _OBSS_]

Hello @zoeyreynolds ,

There are a few common metrics you can use to measure and monitor your team's performance. Among these, the most frequently used metrics are Cycle Time and Lead Time.

Cycle Time: Cycle time is simply the amount of time it takes for a unit of work to go from an In Progress state to a Completed state. The clock “starts ticking” on the cycle time as soon as the work moves from a “Ready” state to an “In Progress” state, and it stops ticking when that work item goes from an “In Progress” state to a “Completed” state.

Lead Time: Lead time is the amount of time it takes for a unit of work to go from an In Queue state (i.e. a customer has requested some work to be done) to a Completed state. The clock “starts ticking” on lead time as soon as the work moves from a “Ready” state to an “In Progress” state, and it stops ticking when that work item goes from an “In Progress” state to a “Completed” state. It includes, and is therefore always longer than, cycle time.

If these concepts sound good to you to use in your teams performance monitoring, let's talk about how you can turn these metrics into a report.

I can recommend Timepiece - Time in Status for Jira app, which is built by my team at OBSS. It is available for both Jira Cloud and Data Center. 

Time in Status mainly allows you to see how much time each issue spent on each status or each assignee. 

  

You can combine the time for multiple statuses to get metrics like Issue Age, Cycle Time, Lead Time, Resolution Time etc. 

The app calculates its reports using already existing Jira issue histories so when you install the app, you don't need to add anything to your issue workflows and you can get reports on your past issues as well. It supports both Company Managed and Team Managed projects for Jira Cloud.

Time in Status reports can be accessed through its own reporting page, dashboard gadgets, and issue view screen tabs. All these options can provide both calculated data tables and charts.

  

I hope you have the opportunity to review and use Time in Status.

In addition, I believe the use case whose link I have provided below will be useful for you to review.

How to get Lead Time or Cycle Time ? 

Kind Regards,

Gizem

[Mehmet A _Bloompeak_]

Hi @zoeyreynolds

Welcome to the Atlassian Community!

You can use cycle time (the time it takes for the team to start working on an issue and complete it) and/or lead time (the time interval between the moment an issue is requested to the moment it is completed) reports to measure team performance. For cycle time and lead time reports, you can try Status Time Reports app developed by our team. It mainly provides reports and gadgets based on how much time passed in each status.

Here is the online demo link, you can see it in action and try without installing the app.

• Cycle Time: You can have a look at Cycle Time by Assignee, Cycle Time by Project, Cycle Time for Each Issue, Cycle Time by Issue Creation Month reports as examples. You can also use Cycle Time by Assignee report for top performers.
  
  
• Lead Time: You can have a look at Lead Time for Each Issue report as example.

For more detail, you can have a look at Cycle Time and Lead Time in Jira: Productivity Measurement with Two Critical Parameters article and Status Time Reports How to Videos.

If you are looking for a completely free solution, you can try the limited version Status Time Reports Free app.

Hope it helps.

[Stanley Duback]

Hey There,

I would say that the easiest way to do this is by creating a dashboard. There are a limited number of reports you can create by default and a number of apps you can install if you need reports that are more advanced.

Simplest way to build a report on that dashboard would be a simple pie chart that sorts all status's by person.