Calculate initial estimate from estimates on child Features
What is the challenge? |
Initial estimate for large capabilities (Epics) does not calculate based on estimates of child Features |
What is the impact? |
|
Describe your idea |
Similar to how the Detailed Estimate field on Epics can be calculated using the estimates of its child Features, the Initial Estimate field on Epics should have option to calculate based on child estimates. For context, my organization uses both Epics (formerly Master Features) and Features. Epics tend to be large capabilities that are challenging to estimate with any confidence. Instead, we estimate at the Feature level and have that rolled up to the overall estimate for the Epic/Capability. These are truly "initial" / t-shirt estimates. However, because of this limitation we must use the Detailed Estimate field. This creates confusion for engineering teams on expectation and challenges with Aha because the detailed estimate field defaults to "calculate from stories." |
8
MERGED
Ability to compute the Initial estimate of an Epic from Features estimates
Who would benefit? All PMs who require to see Initial estimates at both Epic and Feature level but don't want them to be double counted in the "Remaining Work" of a Release. Currently the "Features and epics" option of the Release "Use estimates f...
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved
Having this available would help us more fully adopt Capacity Planning in Aha.
we would also like the option to have the initial estimate on epics and initiatives to calculate from initial estimate on features (or epics for the initiatives) We are using this field, but cannot get good reports as it does not roll up.