What is the challenge? |
What I am observing is that progress on roadmaps appears to be measured based exclusively on detailed estimates as Actual/Detailed estimate. This works great for things that have detailed estimates, but much of our future as yet unplanned work has only initial estimates. The result is that if I have an initiative with 12 monthly features in it all with initial estimates of 10 pts each but only 3 have detailed estimates also equal to 10 pts, and 1 of those three with detailed estimates is Done, the progress on my Initiative is ~33%. What I would like is that Best Estimate (which I understand to be Initial if no Detailed and Detailed otherwise) is used here. In the above case that would provide the correct measure of progress based on available data = 10/120 = ~8.3%. |
What is the impact? |
Progress is incorrectly overstated |
Describe your idea |
Provide a way to measure progress based on best estimate not simply detailed estimate. |
This is a bug, not a feature enhancement. It makes EPICs that are not remotely close to being completed, appear Done on roadmaps when one shows Progress on them. All of our EPICs are set to get their status, dates, estimates and progress from their related features. As our roadmaps go out years, its not realistic to have detailed estimates for features that far out. and while we can use Best Estimate for some things, Progress is not one of them. We are not interested in hearing about any new features until we get the existing ones working correctly and consistently.