RELATED IDEAS
Add releases as an option to the now, near, later roadmap
Who would benefit? |
Roadmap users |
What impact would it make? |
We use releases to indicate the experience being delivered |
How should it work? |
|
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +2
1
MERGED
1
MERGED
Add releases to now next roadmap
What is the challenge? love the now, next, later roadmap addition, but we need to communicate our work at the release level. What is the impact? can't use now, next, later roadmap Describe your idea please add releases to the now, next, later as a...
0
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved
Per other comments, Releases is where the business value of our delivery is most accurately articulated. The ability to report on Releases in NNL would greatly benefit our roadmap communication efforts.
Like the OP and Kalyndra, our organization uses Releases as the 'container for business value.' We operate on a continuous release train where new capabilities, which themselves include various Features, are Released as soon as they're ready. Up to this point I've had to use Pivot tables to visualize something like a "now, next, later" roadmap - our preferred way of communicating the roadmap. I was so excited to see it pop up as a default option, and then disappointed when I realized I couldn't use it for Releases. Good to see that it supports Initiatives -- I'll be using that for internal comms. Thanks!
Please add 'Releases' as a data type that can be put on a NNL roadmap. They can already be rounded to the month, quarter, half, year, but currently individually only. Sometimes features are too granular (and too numerous) for a stakeholder roadmap, and like the original poster our product roadmaps are value-based with the release level being the main data point.