RELATED IDEAS
Allow global initiative rank on strategic roadmaps
Who would benefit?
Product Owners, esp those with Portfolio responsibility
What impact would it make?
Improve Aha! for strategic roadmapping
How should it work?
Me:
I'm very excited by the new initiative scoring and prioritising options:
https://www.aha.io/blog/a-new-prioritization-view-for-product-initiatives
From my parent workspace, I've navigated to Strategy - Initiatives - View Type Prioritisation
I can see that I can update filters to show more than one workspace - and then prioritise across the workspaces in this view.
When I navigate to Roadmaps - and choose a prioritisation roadmap, and sort by initiative rank - the same ranking order across workspaces doesn't seem to be being applied. Instead it seems to be ordering them by an internal ranking within the workpace.
e.g. in my prioritisation view - the 1st 4x ranked initiatives are all from the parent workspace, and the first child ranked initiative is in rank 13
but in my prioritisation roadmap - they are ranked child 1st, parent 1st, child 2nd, parent 2nd etc."
I'd have thought you could also add the rank field(s) to the view directly, instead of/as well as custom fields.
© 2024 Aha! Labs Inc.•All rights reserved
There are multiple places where "sort by Rank" refers to the ordered list of the work item type that you achieve by dragging those work items around; e.g. in the Initiative list, or within a column on an epic or feature board, etc. This has become increasingly cumbersome as new ranking capabilities have been added such as the Prioritization view, the ability to save a prioritized order to a custom field and automated scorecards. Being able to sort a strategic roadmap by any of these would be ideal, but my order, if I had to pick, would be:
By the default scorecard for the type
By and arbitrary field
By some other scorecard field in the type
The manual (drag and drop) rank order
Why? My company used a complex, and automated, scoring system to rank work in order to be able to have roadmaps respond dynamically to a continuous planning cycle. In this model, it is very cumbersome to have to manually drag work items up and down lists every time the something changes the relative ranking. While the manual model is flexible, it does not lend itself to larger working sets. (Or very small product teams trying to maintain a medium sized working set.)
Like the idea being presented as it makes real the prioritization work being done. Potentially expanding the strategic roadmap filter to use any sortable field, but especially the prioritization ranking.