We're using a (value / estimate) method for determining the score of a feature. The division usually results in a decimal point (so one feature is a score of 3.1, another is 3.4). Right now, Ahah is turning both into a 3.
We'd like to be able to show one decimal place of score. Right now we're multiplying by 10, but that's making for some confusing (high) priorities, as we use the one decimal place score in other places in our company.
Yes please - absolutely. Decimals make all the difference for us
This would be very useful for my organisation as we calculate effort based on man days which can go up to 200. Typically this means even a basic value/effort score comes out as a decimal and is just rounded up to 1 every time. Workarounds are in place but not ideal.
Seems like an obvious thing which should be enabled (or a choice to round up or down to a whole number). Without this, the scorecard functionality is really limited.
Same for us, I came from Azure boards where I had configured a variation of the RICE score using some other variables, with decimals involved. Looks like I'll need to change the calculations in aha.
Agreed. We were using a two decimal place score for Desirability and Viability to calculate Business value. ex: 2.84 In order to not lose score granularity in Aha! we had to move from a 1 - 5 scoring range to a 100 - 500 range with the result being 284 instead of 2.84 Not ideal.
I would like to see 2 decimal score. As some mentioned before, AHA! shows lots of features with same scores, which is hard for us to know which one is more prioritised.
Like others have mentioned forces an over simplification of the RICE scoring system, and will force us to make changes to our scoring process based on the limitations of Aha.
This would be extremely helpful for putting in a wsjf score
We also wish to properly implement the RICE scoring methodology. It's complicating things greatly to not be able to use the 'regular' RICE scoring in AHA.
Our company is standardizing on the RICE scoring methodology and being able to use decimals in scoring is essential. While we could substitute the typical RICE values for integers at the same factors, our investors are mandating the same scoring methodology across their portfolio of companies. So we need to use the typical decimal values of RICE.
I would also like to be able to use decimal points in metrics for the scoring.
Aha! is giving me integer numbers for all and there are a ton of each of the integers, but not much differentiation between them. When I had this in my staging spreadsheet, one decimal place really helped show the strata within the integer values.
We've found even with very large (e.g. $10k unit) increments in the scorecard, there's still a valid use case for using decimals.
Use case: We use a 1-5 scoring 3-point system to create a total score so used to using a decimal point scoring system. As you don't have this feature we've had to change the way we score and evaluate new product feature requests. Would be great if we had the flexibility to do this in your tool.
This is a big requirement because without it there is now way to implement RICE methodology cleanly
Agreed, decimals are desired. Two decimal places please, AND ability to represent RICE Confidence percentage as a decimal instead of a whole number percent.
We are planning to use RICE scoring. For 'Confidence' we want to use decimal like ".50, .75, 1" to represent the percentage. This returns results like "6.75". With the current function we must represent percentage as "50, 75, 100" which instead returns "675". The information is the same but it is visually and conceptually easier to compare scores with lower numbers and decimals associated.
We're trying to get rid of an ROI calculator (spreadsheet) we use and move our whole roadmap process into Aha!, but just reached our first deal-breaker to that - this ticket. It rounds all the initiatives to basically the same score, so we gain nothing from our custom equation.
Please please please support decimals. For WSJF, there is no clear ability to discern priorities rendering Aha! in effective. Big problem.
Please add this for use with WSJF.
This is becoming an impediment now and preventing our Product Managers/Owners from using Aha! - Is there an update on when they Feature will be released?