What is the challenge? |
From a product planning and version management perspective, a product is divided into areas, each with a set of capabilities organized in categories. Each capability has features that evolve and are linked to an initiative and goal(s). (each feature has its set of user stories/requirements / U). |
What is the impact? |
This would enable PM teams to better organize their product feature tree within an area of the product. |
Describe your idea |
Allow organizing epics in categories based on relevant topics while allowing viewing the associated epics with their features and user stories in relevant boards and reports. |
Recommend to merge with this idea: https://big.ideas.aha.io/ideas/A-I-13471
100% Agreed. This is usually referred to as a capability area for us.
Why do capability areas matter?
They provide a functional/technical view of the product and thus help refine larger epics or initiatives, which usually cut across multiple capability areas and represent the process view. So, that's a view that our architects and engineering managers frequently require.
In RFPs, customers usually ask for features within a capability area - would be nice to quickly filter for that.
Current Workaround:
We have created a custom table for this which we need to maintain. We add them as a label to the epics, and an epic can have multiple capability areas. For the capability area, we have a description and sometimes even a small PRD or ACD as linked artifacts. We pull reports on capability areas to see all the past and current Epics related to this, and our user stories are usually sliced by capability area.
Suggestion:
As this is something that I have seen in many organizations, it would be nice to have a more standard record type for this, which can be managed with proper views. I would also really like to see it a part of the header menu, to be able to navigate to it easily. Alternatively, it would be nice if record types based on custom tables could be added/'pinned' to the header menu, so they can easily be found and navigated to.