RELATED IDEAS
Change epic's date range on a strategic roadmap for each initiative that it's under
Our firm tracks goals as financial objectives, then initiatives are things to achieve those goals, and epics under initiatives. We report in this way.
However, in our world - pretty much every initiative will have the same epics. For example a bond has asset servicing, so does a swap, so does digital assets - basically of the 50-60 asset classes we have to eventually build - all of them have an asset servicing component. We want to avoid thousands of epics - but find that if we have one AssetServicing epic - with features in it from multiple initiatives - when we report on the roadmap for say the FixedRate initiative - the epic dates go all the way out to asset classes we won't deliver till 2027.
If we make an epic for every asset class initiative - the dates are correct - but the growth of epics is crazy. Ideally we'd want the epic timeframe on the roadmap report to be filtered by the initiative its in - so that I could have 1 asset servicing epic for all of my asset classes - but the date range would be filtered to only the asset servicing features in that initiative on a strategic roadmap.
Said more generically - you can have repeating bodies of work that relate to a specific initiative. That body of work may have to happen on many initiatives but today you cannot separate them instead of naming that work differently per item. The goal is to enforce a hierarchy of features -> epic -> initiative such that an initiatives timeframe, and an epics timeframe is a subset of all items under the epic and initative. I.e. an epic could cross many initiatives - however, in a roadmap view we need a way to restrict the start and end time to only features in that initiative.