Estimation accuracy

[Lena Sargsyan]

Hi all,

I want to measure estimation accuracy of our engineers. It may be the ratio of the original estimate vs time spent or better due date vs resolve date. How can it be implemented? please advise. I know about the workratio but it is not clear what does it measure because even if my tasks don't have time spent logged it includes those tasks in the calculation as well.

Thanks.

Lena

[Danut M _StonikByte_]

Hi @Lena Sargsyan,

I think you can calculate this at the team level or at team member level by using the Advanced Issue Filter Formula gadget offered by our Great Gadgets app.

Here is how to do it:

• have a Jira filter that includes the issues from the team  or a person. It should include only the closed / resolved issue, because the open or in-progress issue will not have time spent yet, so they are not relevant.
• configure the gadget to calculate in variable "a" the average or Original Estimate for the issues in the filter. Calculation is done in seconds, but you can transform in hours by dividing to 3600.
• configure the gadget to calculate in variable "b" the average or Time Spent for the issues in the filter. Calculation is done in seconds, but you can transform in hours by dividing to 3600.   
• calculate and display the accuracy by using a formula like this (b/3600)/(a/3600)*100

This will result in having these numbers displayed on your dashboard:

 

A ratio of 112.9% indicates that the team spends 12.9% more time than it was estimated.

I hope this works. If you have questions, please don't hesitate to contact us at support@stonikbyte.com. Please remember that this app offers many other gadgets that you will find useful. 

Thank you,

Danut Manda

[Lena Sargsyan]

Thanks @Danut M _StonikByte_ for providing  a great solution. However, currently I am not ready for extra costs. And was rather expecting that there should be a built-in solution to my problem. That is why  I approached to the Atlassian Community hoping that there is something I am not aware of.

[Bill Sheboy]

Hi @Lena Sargsyan 

How often do you want to measure this?  What would you do differently if you had this information right now?

Knowing the answers to those questions may help you decide solution approaches.  For example...

• If you need this one time for a conversation with team, perhaps export the issues to a spreadsheet for analysis / reporting.
• If you need this more often, perhaps use an automation rule to calculate the values at the end of a sprint / time period, and use that for conversations.
• If you need this all the time, perhaps add a custom field and an automation rule to calculate the value when items complete.  This information could then be reported upon.
• If you need more complex analysis, please investigate the Atlassian Marketplace for better reporting / analytics tools than are built into Jira.

Kind regards,
Bill

[Lena Sargsyan]

Hi @Bill Sheboy 

I need this once per 6 months for the 6 month period.

Basically, in the engineers performance analysis we have a point  about their ability to estimate the tasks with 30% accuracy. That is why I wanted to make that parameter measurable and control the requirement somehow.

We don't have sprints - just Kanban boards for the different company-managed projects.

Thanks. 

Lena