RELATED IDEAS
Introduce fibonacci number format for estimates and scores.
Many scrum teams adopted relative estimation points for effort and business value based on Fibonacci numbers (or in some cases for Business Value the Fibonacci number mulitped by 1000).
It would be great to build this into the scores and capacity planning model.
Brian: setting the scale is one thing, but I would really like the software to enforce the scores, if possible. We use 1, 2, 3, 5, 8, and 13 here. Ideally, in the Scorecard editor, we would provide a list of all of the permissible values for the slider (i.e., "1, 2, 3, 5, 8, 13").
For now we're using the 1-10 score, and telling people not to choose 4, 6, 7, or 9, and using 10 as a proxy for 13 which means "break down the feature smaller" anyway so it's transitory. But it would really be nice if the software didn't have to make us think about which numbers were allowed and which weren't.
If we allowed you to set this scale for metrics that are used in the Aha! Scorecard would that suffice? Note that I am differentiating that from allowing this scale to be forced when using the feature estimator capability -- which btw, you could just train your folks to use the Fibonacci there even if it was not enforced by Aha!