You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
In looking at the WSJF numbers, rounding at two decimal positions appears to be performed.
In reviewing numbers, sometimes the value is rounded in the standard manner but sometimes it is rounded down and sometimes it is rounded up instead.
With no apparent logic.
Just noticed (this is the cloud version)
If you enter the numbers from the Feature Estimation page it works properly.
If you enter the number from the Feature details pane, it does not.
If you enter the numbers from the Feature Estimation page and then go to the Feature detail pane, the numbers on the detail pane will be recalculated on display.
etc. (I am not going to figure out all the nuances of this).
Jeffrey, I was able to reproduce the 3rd decimal number rounding issue
In one instance it appears to round and the other it appears to truncate.
I'm happy to submit it as a bug on your behalf.
Everything looks good for the 1st and 2nd decimal number calculations.
Jeffrey, I just wanted to let you know that your rounding issue is officially on the internal team's backlog to fix. I don't have a commitment date but know that you did find something.
The workaround is to have additional conversations, when epics have a WSJF score that is the same (out to the 3rd decimal point). Being the inputs are following a Fibonacci series, the output is to support a relative comparison, to support you in your prioritization endeavors.
Could you please post a picture of the values in question, to allow us to further investigate?
Just post a picture here that looks something like this:
Jeffrey, I agree with you.
That does not look right. I did the same calculation and I get 3.63.
This could be a bug that has been resolved.
I'm on Cloud 10.75.
What are you running?