7

1

Is it possible to split out estimation history by case category type? If it isn't, I would like to request it as a feature.

The value of this might not be immediately obvious when the standard workflow case categories are used. However, we are planning to use a custom workflow, with a different set of category types. Inherent to these categories will be that some are more complex and less predictable than others. Because of that, we expect that for all users, there will be poorer estimation accuracy for some category cases than others, and the estimation learning curves will also therefore differ between categories.

If we can capture and analyse estimation history separately by case category type, we would expect great gains in project planning. Consider this example: The users working on cases for a milestone have estimation histories primarily based on working on cases from the "more predictable" case categories. So their estimation accuracy is pretty good. However, this milestone has a higher-than-average proportion of cases from the "less predictable/more complex" case category types. In this situation, the users' estimation history/accuracy will provide an overly optimistic estimation of how long it will take them to complete the cases assigned to the milestone, as their "overall average estimation across all case category types" is used. However, if we had been able to take into account the fact that these users will be working on cases where their estimation history is less accurate, then the estimated milestone completion dates would be more reliable.

Fog Creek Case FC2048336

flag

1 Answer

0

Agreed. Right now EBS history partitions at the 4-hour mark to separate history of sub-4-hour estimates from bigger ones, and separating on case type is a proposed feature for the next version. Probably the idea will be to separate on case type as soon as a user has enough data in the system for that case category to generate a reasonable distribution without including data from other case categories.

link|flag
Given sufficient data, it would be great to be able to slice and dice EBS along whatever discrete dimensions exist in the data (or whatever ones can be imposed, like the 4-hour cutoff you mentioned). Being able to do so would allow EBS to become more of a reporting tool rather than primarily predictive, as it is now. – cdeszaq Mar 12 2010 at 13:39
Agreed, and this is provisionally part of our current plan. – Brett Kiefer Mar 12 2010 at 13:49
Sounds awesome! Can we have it now please?!! Seriously, do you have any information on where this sits in the priority list and when we can expect it? It would be useful to know, as having this could tip the scales in FogBugz's direction for a number of project groups where it is currently not used. – Prop Joe Mar 14 2010 at 19:26
Sorry, as you know, we try to be as disciplined as we can about not committing to dates. I know that this can make things difficult for planning, but we really believe it's the best way for us to keep working as hard as we can on the most important things. – Brett Kiefer Mar 17 2010 at 16:46

Your Answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.