A release can be across multiple initiatives and is displayed as such in the portfolio roadmap. If a release has 6 features split across 2 initiatives, it will be very useful if the portfolio manager is able to see, when rolling over, how many of the features within the release relate to the initiative the release is displayed within.
For example, release 1 has 6 features. The release is split to have 4 features for initiative 1 and 2 for initiative 2.
When rolling over release 1 of initiative 1, there is a line which specifically states "4 of 6 features related to initiative" where the word 'initiative' will change according to product terminology.
Underneath here it states "3 of 4 features implemented related to initiative".
The result is the portfolio manager is able to get a very clear picture as to which initiative is being focused on more over another, and whether this sits with strategic priority.
|Release time frame|
Thank you for your idea. This is not currently planned on our roadmap but we will continue to monitor customer feedback. In the meantime, we would recommend creating a pivot table of features by initiative. You could add this as a page in a notebook following the portfolio roadmap view so that the portfolio manager could drill into more detail by moving to the next page.