RELATED IDEAS
Using estimates to power progress meter
We use initiatives to track progress at a high level. The initiatives contain master features and features. Each feature is estimated in story points and no 2 features are the same size. In the current scenario, if I have 10 features within an initiative and 3 are shipped, the progress meter would show 30% complete but that is inaccurate because each feature is not the same size.
It would be great if master features and themes can report progress based on the estimates of their child records.
example: If an initiative has 10 features that are estimated at a total of 100 points and 5 of the features totaling the estimate of 25 points are complete, the progress meter should show 25% progress (not 50%).
© 2024 Aha! Labs Inc.•All rights reserved
This is a superhelpful to measure the progress.
Has there been any movement on this idea?
Requirement, feature and master feature completion should contribute pro-rata to overall initiative progress based on their individual story point or time estimates. Not using the weighting of items could create a false progress indication.
Agree with Samir, this feature would bring extra granularity and visibility that our Executive and C-Suite stakeholders are seeking as they're tracking Company level Goals and Initiatives.