Many intiatives may benefit from some common functionality. If you could add a feature to multiple initiatives it would allow you to better track the impact of the feature across the entire business.
need it because many of our features belong to multiple initiatives.
Because we want to show how a single feature in a product release, delivers value / unlocks initiatives at different levels in our planning architecture.
A feature can be associated with an initiative to deliver a complete solution in some space, as well as be associated with an initiative that delivers a similar solution in another space along with helping to reach a 'strategic initiatives goal' at the highest level.
Limiting a feature to belonging to a single initiative prevents us from planning common work such that everyone understand the complete impact of delivering a feature.
We have features that can belong to multiple initiatives, goals and such features add more value and can be prioritized. Showing a count of linked initiatives, goals can also help with the prioritization.
Definitely need this, right now our product managers have to select 1 initiative for a feature, then when comes to reporting they are having to manually create a report showing the impact of a feature across multiple 2-3 initiatives and all goals...Wasting a lot of time that is better spent else where.
It would be good to know if this will be implemented, as most companies have features that will span multiple strategic initiatives - even more so if they have department(local)/region/global initiatives that are heavily related to each over.
For example initiative for a global roll out of a release, will have features in each localized area which apply to a local set of initiatives for that region as well as adding to the value of the global initiatives of the product roll-out which also adds to other company strategy, sales & support readiness initiatives.
Once multiple initiatives are done, Aha, becomes indispensable for us and many other companies like us at a strategic operational level.
Any movement on this? This is a really useful option. Features that can satisfy multiple initiatives can be on higher priority.
I agree with all of the others who have posted on this issue. Many of our features are linked to more than one initiative. Having this information in the system will make it easy for us to determine the features that are helping to satisfy more than one initiative. It also will allow us to easily get access to the initiatives from the features and vice versa.
Taking the example from the Fredwin Software (demo), consider the feature “Share places of interest in Italy”, this could be attributed to the initiative of "Launch Giro d’Italia site". However, it could also be linked to the initiative "Support Galileo GPS system" as that is the technology used to detect where you currently are to show the places of interest closest to you. Similarly, the initiative "Mobile Fredwin Cycling Tracker App upgrades" may also have to be adapted to support this initiative.
I understand that the issue of restricting a feature to only one initiative was to cater for future plans for capacity planning. However, isn't capacity planning going to be driven at the feature level, irrespective of how many initiatives a feature it belongs to?
I note that on Mar 20, 2015 it was indicated that you were 'likely to implement' this idea. Any idea when this is going to happen ?
I agree, it seems an obvious use case that a well-planned feature could contribute to several initiatives
Yes this is an important one ... we need to have multiple initiatives linked to a feature !!!
get this done please :-)
+++ for this feature
Our Company uses the Features board to track/manage "projects" as opposed to individual features. So the idea that features and Initiatives should only have a 1:1 relationship doesn't apply here. Looks like a lot of customers here are using aha in the same way.
As such, we need to be able to align "projects/features" with Product strategic Initiatives as well as Company strategic initiatives, so there is clear visibility. This becomes even more important as we utilize reports to communicate to the rest of the company and the board our progress against strategic objectives.
This would be really useful for us. We've found a way to work around for now which allows us to see what we need at a feature level, but we can't see features from the initiative.
This is a big need, especially for larger enterprise implementations. Any status on when this is "likely to implement"?
Dear AHA product people, please disclose where this feature request sits within your roadmap ;-) This is requested and pending since early 2015 and still customers keep bringing up their need.
Really need this. Many planned features will support multiple initiatives but aha can't represent that.
We have many features which belong to multiple initiatives. This is almost a basic level requirement for us to track anything within aha!
For us an initiative is a specific area of focus that will help us reach a goal. For example, "create frictionless onboarding for customers" is an initiative. And then also "reduce calls to support" is another one. We could have a feature that we want to associate with both initiatives.
You can do this on a release. We'd like it on the feature as well.
This would help sell to senior leadership the desire to work on something by being able to show that working on one Idea or Feature is addressing multiple initiatives at the same time. Senior leadership loves to know when something is killing two birds with one stone.
We have multiple initiatives at the corporate level and some features we're delivering span those initiatives even if they are secondary benefits. From the initiative level we have higher decision maker users who want to see a few of an initiative and all the features that help support and move that initiative forward in reporting.
I wish John Biltcliffe would have shared his work around. We desperately need this
You won't be notified about changes to this idea.