RELATED IDEAS
Show dependencies in the Custom Roadmap and Pivot views
We have an internal technology group that releases core functionality that other products are dependent on. I need to be able to show that to the execs so they can visually understand one of the internal constraints of delivering the product.
This is a Release to Release dependency.
As an example, in the good ol' days BA (Before Aha!), we'd do something in powerpoint like the attached.
-
ADMIN RESPONSENov 3, 2022
Gantt and strategy roadmaps now show other dependencies related to your work. This update exposes connections to records beyond your filtered view — fostering increased transparency across teams. Use these popular views to quickly identify and mitigate risks to move forward with confidence.
https://www.aha.io/blog/a-better-way-to-visualize-cross-team-dependencies-on-roadmaps
It sounds like this idea is for showing dependencies on pivot reports so we will keep it open to continue monitoring feedback.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +67
15
MERGED
Show Dependency Line on Custom Roadmaps
Although functionality was added to show a pop-up of a grid of dependencies from the Custom Roadmap, this doesn't solve the need to have the connector lines representing dependencies, so we can have a simple, static visual of the roadmap. The Stra...
2
Planning to implement
11
MERGED
Develop a way to show release dependencies in Roadmap views
We have another group in the company that develops core technologies which are used in some of our products. We frequently use the Timeline view for internal planning and would like to have a way to show that a product release is dependent on the ...
0
Planning to implement
We have had to build custom roadmaps to be able to see the work that our teams are doing based on initiatives, and the dependency feature is a critical missing piece of functionality. The strategy roadmap isn't powerful enough for our needs, but has this functionality. We're forced to use a combination of the custom roadmap and pivots to highlight the dependencies instead of a single view.
We would like something similar but would also like the ability to show the Features in boxes on the timeline and have them linked together by their dependencies.
From this request I'd like to see the visualization of the relation of features, releases, master features, etc. in a larger canvas. Something like what you can already see in the "visualize" area of each feature with respect to linked records, but say on a whole product line, or even better across all of Aha. In my case, I am running a Platform network of websites, described here:
https://support.aha.io/hc/en-us/articles/217140266-Best-practices-for-managing-platforms
What would be ideal is to be able to see these dependencies across all the go-to-market products that interact with the individual features, and in particular master features, of the product that is the platform.
Thanks guys!
From a PMO standpoint, we would like to use Aha! to show a Project Initiative based Roadmap showing a summary view of all Project Initiative Dependencies on the Roadmap View. We want to build one Roadmap View showing all of our Product Initiative and Project Initiatives associated with our Organizational Goals on one Dependency Roadmap View.
Technology is one driver to Roadmaps but there are more. Generally, a good "technology roadmap" for a product portfolio shows Features, Technologies, Skills, Staff, Funding, Calendar Events, and Disrupting Threats. The two screenshots (from PersonalBrain) show a few of the kinds of roadmaps that are needed. This paper (one of several like it) http://www.vgu.edu.vn/fileadmin/pictures/studies/MBA/Handbook_Roadmapping.pdf illustrate a few of the common needed patterns.
Generally, one must be able to show the evolution of multiple facets of a solution domain (capability, technology, economics, skills) over time on the same graphic AND show the dependencies between the facets.
Only then can an Enterprise Architect, a Product Owner, a Project Manager, a Scrum Master, or a Buyer answer the crucial "What if?" questions.
So +100 for the original poster's capability request. What's the ETA?
I would also like to show the reverse. If we plan to create an experience next year, but the technology group hasn't yet planned the technology that will be needed, we'd like to have some way to show that there is a gap or a need.
I requested something similar