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.
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.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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!
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