Is there any configuration in Jira Agile saying one story point is equal to 'n' number of hours.

For Estimating and tracking, we are estimating the issues using story points and Tracking using hours. So we would like to know is there any setting in JIRA Agile saying that a story point is equal to a number of hours.

 

3 answers

1 accepted

This widget could not be displayed.

In principle a story point should never be expressed in hours. It's a relative measuring instrument. Therefore it would surprise me if such a setting would exist.

Dennis is not going to be surprised.  Story points are not hours, and there is absolutely no equivalence anywhere in JIRA.  Because it's wrong.

Hi All,

Thank you so much for the update. Since JIRA has the multiple options for  Estimates(Story points,Original time estimate etc .,) and Time Tracking drove me to this question. Thanks for the clarification.

Vijay

This widget could not be displayed.

I think the friction you are encountering is that if you are using Story points.   There is an average standard deviation that predicts the number of days something with "X" complexity takes.      This avg is how you should communicate to the business what the estimated date of completion might be..   The goal of Story points is to ensure the Dev team is focused on building great things.. while keeping the business informed with predictable results.    In My Experience when you start trying to cut out extra steps by "crossing the streams"  of 10 SP = 5 days..  The end result is that that business then drives the creative process straight into the ground as everything should be a straight conversion factor.   This results in developers worrying about logging time or if they hit the estimate instead of Quality and Innovation.      In recap   Story points are complexity.   a 5 of complexity does not have the same avg days of engineering as a 13SP item or a 1SP item.   The failure comes when you say a SP is equal to a constant value.      In conclusion every team will have a different burn rate based on complexity vs engineering hours.  Does that make sense?   Of course others may disagree... but this is the best way I have found to break down the conversation. 

Hi ,

Thank you so much for the information. 

Thanks,

Vijay

This widget could not be displayed.

Hi All,

There is the 'Story Point Cheat' suggested by Dan Chuparkoff:

30 mins  = 1 story point

1  hour  = 2 story points

2  hours = 2 story points

4  hours = 2 story points

1  day   = 16 story points

2  days  = 32 story points

3  days  = 48 story points

https://youtu.be/NrHpXvDXVrw?t=9m51s

 

 

That completely misrepresents what story points are for.  They are not hours.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Tuesday in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

172 views 1 3
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you