RELATED IDEAS
View feature board for all sub-products at the product line level
We would like to see the feature board at the Product Line level for all products within the product line, including the ability to drag/drop prioritize and view details of each requirement.
-
ADMIN RESPONSEMar 10, 2016
Currently, the feature board is set at the product level to help with prioritizing features and releases for each product. This allows a focused view into feature prioritization at the product level.
It's also possible to create pivot reports which show features across releases and products (though drag and drop prioritization is not available from the reporting screen).
At this time, we are unlikely to make updates in this area due to current priorities and community feedback. We hope you can understand.
7
MERGED
Multiple Product Feature boards automatically updating a Master overview Product feature board
I have several roadmaps for different product lines - there is some overlap between them (resources, technology enablers, features) so want to have a single Master overview of the combined product lines. Updating a feature/release date etc on a sp...
0
Unlikely to implement
10
MERGED
Prioritise Features on product line and account level
Especially in Agile development environment, the priority of a feature is regularly reviewed and changed, e.g. because new features are created all the time and need to be included in the schedule.
Now, features can only be prioritised on the feat...
0
Unlikely to implement
© 2024 Aha! Labs Inc.•All rights reserved
Please reopen this idea and reprioritize. There is no suitable workaround for planning work across an entire product line.
Currently, we're stuck doing all of this work outside of Aha! (in Excel with a series of calculated fields to handle the scoring and capacity).
Agreed, this is a must have for those practicing Scaled Agile Framework (SAFe). This would give users the ability to have a Kanban board and prioritize PI's across teams. Currently a user has to prioritize in individual products, then pull a report to combine all products, and prioritize from a report instead of in a real-time kanban board.
This is definitely a "must have" if you're building an application that contains multiple services and tiers. If Aha! is not going to at least implement swim-lanes or a master features view across multiple products in a product line, then we have to abandon Aha!
Any plans to revisit this?
What we are challenged with right now is having a single board view where we can look at all items under consideration/in design and drag and drop priority across all products. Going through individual products is not an option. We have had to pull things out of aha and do the prioritization in a spreadsheet for now.
I agree that this is something that's also critical when trying to scale to many products. Engineering and business analysis resources need to be prioritized across the product line, so very often just viewing an individual product's priorities is not enough. It would be very helpful to be able to prioritize across the product line in the drag and drop fashion. I don't see any downside to having an optional feature board at the product line level that could aggregate master features across products.
Agreed that is a must have for all product managers to view and score and prioritise together when there is a master feature board containing features from other product roadmap for engineering to use instead of creating pivot table.
Kind of a "must have" for those practicing Scaled Agile Framework, or SAFe. The pivot report just doesn't work very well.