Why is it useful?
For each release, we create a phase for each sprint, and generally assign features to sprints - especially for features that have dependencies.
This helps us manage feature dependencies across products (and within products also).
It would be helpful to have a visual representation of how we are progressing (using story points) for a group of dependent features.
Who would benefit?
The PMs would have better visibility into how we're progressing on dependent features, and a better understanding of risks.
In other words, if Feature A is dependent on Feature B, if Feature B is not progressing, this will improve visibility into the fact that Feature A may be at risk.
How would it work?
I see this working similar to the way that we show progress on the home page - where a bar becomes darker, as the number of features is completed.
However, rather than basing the progress bar on the number of features, a percent of story points completed would be more helpful and more accurate.
|Release time frame|
Great news! It is now possible to track progress on goals, initiatives, releases, release phases, master features, and features. The percent completed can be entered manually or automatically calculated based on related records and can be visualized using progress bars on roadmaps.
Check out the blog post for more details.