RELATED IDEAS
This idea has been merged into another idea. To comment or vote on this idea, please visit APP-I-4755 Release and Feature Management Change Log Reports.
Have a baseline option to be able to see slippage in plans
Merged
Knowing the plan is one thing, but knowing how far off plan we are is another to help make decisions on diverting resources. Please provide a means of seeing baseline vs current without having to create two notebook pages.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +13
56
MERGED
Report to show original planned release and current release or actual release
It would be great to see the Release a certain feature was marked for and when it was released later.
This would be helpful to see how many features are moving or slipping original planned releases and help figure out why thats happening
I think y...
5
Shipped
Adding my voice here. Knowing your roadmap, and the variance to the plan is critical to understanding where energy needs to be applied to meet our companies objectives. It is very difficult to clearly see where we are getting repeated slippage so we can track our dominant constraints.
This also sees very similar to https://big.ideas.aha.io/ideas/APP-I-1904 ?
I received a notification that this idea was shipped. One, is that true? Two, we need this more than ever. Effectively measuring churn is a complete bear.
Same here, doing screenshots to do manual comparisons...
Bumping this idea up. We find ourselves taking screen captures and other options to see committed features associated to releases. This serves as the basis for our change management and KPI but definitely see the opportunity to have this more programmatic within Aha itself.
Hi Nathaniel, depending on your exact needs there are a few options you may consider. I'll ask our customer success team to reach out and discuss those options with you.
Having this capability will make it far easier to position Aha as an Enterprise solution for product management. If this solution is not on the roadmap, at least provide an alternative (aka work around) that can serve as the temporary so we can avoid having to revert to Microsoft Project
As part of the roadmap improvement process, we need to be able to track and compare planned versus actual roadmap attainment. We are trying to get better at roadmap delivery and we need some way to keep track of "what was promised" rather than, this is the current one.
Definitely useful. Roadmaps and changes to roadmaps help to visualise success or analyse reasons why things have changed
raising this issue again--adherence to the plan and showing changes would be a valuable addition for complex projects
Our board measures us on a KPI of progress against roadmap. Without the ability to see when people move features to a different release, this is really hard to measure easily. Having to visually compare two notebook pages is not accurate or easy enough.