How to measure Issue time in progress until done vs story point by assignee?

[Aron Kurovski de Castro Paiva]

I would like to better understand each developer's productivity.
I understand that each developer has their own perception of complexity and level of seniority, each user story is subjective.
My idea is not to compare results, or compare productivity, but rather to have individual understanding and be able to help developers improve their skills and be more accurate in relation to upcoming activities.

[Valeriia_Havrylenko_SaaSJet]

Hi @Aron Kurovski de Castro Paiva  👋

Welcome to the community! 

For this i recommend you to try Time in Status for Jira. In Sprint Report feature "Workload" section refers to the volume of work assigned to individual team members.




Here you can better understand each developer's productivity.



Also Assignee time report will help to have individual understanding and be able to help developers improve their skills. The Assignee time report shows the total time a particular assignee has been working on the issue.

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

Hope it helps 😌

[Mehmet A _Bloompeak_]

Hi @Aron Kurovski de Castro Paiva

Welcome to the Atlassian Community!

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. For further details, you can have a look at Status Time Reports How to Videos.

• This app has a dynamic status grouping feature so that you can generate various valuable reports as time in status, time in assignee, status entry dates and status counts, cycle time and lead time, average/sum reports by any field(e.g. average in progress time by project, average cycle time by issue creation month).

• You can search issues by Project, Issue Type, Status, Assignee, Issue Creation/Resolution Date(and any other Date field) and JQL Query.
• Status durations are calculated according to the working calendar you define. Once you enter your working calendar into the app, it takes your working schedule into account too. That is, "In Progress" time of an issue opened on Friday at 5 PM and closed on Monday at 9 AM, will be a few hours rather than 3 days.
• You can set different duration formats.
• You can export reports in CSV file format and open them in MS Excel.
• You can also add this app as a gadget to your Jira dashboards and reach “Status Time” from Issue Detail page.
• You can enable/disable access to Status Time reports&gadgets and Issue Detail page per project, users, groups or project role.

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

Hope it helps.

[Amay Purohit_RVS]

Hi @Aron Kurovski de Castro Paiva 

Welcome to the community and Happy Christmas !!

If you wish to consider a mktplace app to determine the time taken by each developer/assignee to complete tasks, you can try out 

Time in Status Reports 

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

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

[Gizem Gökçe _OBSS_]

Hello @Aron Kurovski de Castro Paiva ,

Welcome to the Atlassian Community!

In order to measure and understand your developers productivity, 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 and on each assignee. 

Time in Status offers two report types for your case:

The first one is Assignee Duration or Assignee Duration per Status reports  which shows how much time each assignee spent on each Status. These reports show a list of issues by default so you can see the metric values for each issue separately. Please refer to the screenshots below.

             

As an alternative approach, Time in Status also has Duration Between Statuses report type which shows the duration between two specific statuses. This report type also allows the user to exclude the times for "pause" statuses. You can combine the time for multiple statuses to get metrics like Issue Age, Cycle Time, Lead Time, Resolution Time etc.

For example, in the screenshots below, the Duration Between Status report shows the total monthly response and resolution times for each assignee in a project.

 

For all numeric report types, you can calculate averages and sums of those durations grouped by the issue fields you select. For example response time per assignee or average resolution time per sprint, week, month, issuetype, request type, etc. The ability to group by parts of dates (year, month, week, day, hour) or sprints is particularly useful here since it allows you to compare different time periods or see the trend.

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.

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. And the app has a REST API so you can get the reports from Jira UI or via REST. Also you can export the reports in to various formats easily. 

Visit Timepiece - Time in Status for Jira to explore how our JIRA add-on can revolutionize your metrics measurement process. Enjoy a 30-day free trial to experience the full range of features.

If you wish, you can also schedule a live demo. We will provide a comprehensive overview of the application and address any inquiries you may have.

Hope it helps,

Gizem

[Danut M _StonikByte_]

Hi @Aron Kurovski de Castro Paiva,

Take a look over the gadgets offered by our Great Gadgets app.

This application offers many gadgets that you can use to measure team productivity as well as individual productivity.

For instance, you can measure the time between In Progress to Done for each developer by using one of these gadgets: Cycle Time Trend, Control Chart or Histogram Chart.

You can also measure the number of story points burned by each developer by using the Kanban Velocity / Throughput gadget.

All you have to do is to configure these gadgets to use a filter/JQL for the issues assigned to the user (John Smith in my examples). You could have a dashboard In Jira for each developer.

This app offers many useful gadgets for tracking agile projects, so it can be a great asset not only for you but for the entire team. Have a look over the articles from our blog to make a better idea about how many things you can track with this app. 

Hope this helps.

Thank you,

Danut

[Bill Sheboy]

Hi @Aron Kurovski de Castro Paiva -- Welcome to the Atlassian Community!

Have you considered having a conversation with each individual, to learn where they believe they need to improve based on expectations for the team, and perhaps supplement that using data from the built-in control chart?  Using a quick-filter on currentUser() could focus the view to one person when having the conversation.

https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-control-chart/

You also note "be more accurate in relation to upcoming activities."  Does that mean the people are individually forecasting work / effort, rather than working together as a team to deliver value?

Kind regards,
Bill