RELATED IDEAS
Dependency Tree for features
This may be something you already have but I haven't discovered it yet. As we build out our roadmap, there are clear dependencies between features, sometimes several layers deep. We can specify those dependencies within each feature. However, it would be great if the dependencies could be mapped to a visual dependency tree to highlight the sequence that features need to be developed in. Also make it clear to stakeholders who always ask for the stuff at the end, to show them the sequence of steps that need to happen first! I've attached a screenshot of the type of diagram that would be great.
4
MERGED
Show feature dependencies in Features Board view
The visualization for feature-to-feature dependencies in the Releases Portfolio/Roadmap view is great, however, it would be even more helpful to have the ability to view these dependencies within the Features Board view, since this is the view tha...
0
Shipped
4
MERGED
Tracking Dependencies in more detail in the features list view or pivot table
We would like to be able to show "Related features", "related feature release" and "related feature release date" in the same row. Right now on the Features List view, we can add related features, but it doesn't give us the detail of those related...
1
Shipped
21
MERGED
2
MERGED
Allow Phases and Features and Milestones to be connected as dependencies
I was wondering if in the future it will be possible to connect phases and features as dependencies in the Release Roadmap? It's really the best view for achieving critical pathway within Sprints because of the dynamic dependency linking; the Feat...
1
Shipped
4
MERGED
High-level visualization of dependencies between releases
I would like to make a high-level visualization of the dependencies between different releases, similar to the attached diagram.In this example, I have two different product lines (A and B), each with multiple releases. The releases in these produ...
0
Shipped
© 2024 Aha! Labs Inc.•All rights reserved
Hi Chris,
My diagram was being a little loose. I suppose internally here we
distinguish between a bedrock "feature" that needs to be implemented, and
then additional use cases that require additional work on top of that. The
term feature/requirement/use-case are all inter-changeable. In terms of how
it might work, I'd imagine something like:
- select any feature or requirement
- display all linked dependencies (into and out of) this feature and any
related features
- so you're basically following the dependencies in all directions,
until they reach the end, and then displaying them in a visual way
cheers
darragh
_____________
*Darragh Smyth*
Product Manager @Swrve.com | *phone*: +353 (87) 369 0484 | *skype*:
darragh.swrve
Thanks for the idea submission. Dependency mapping is something that has been asked for a couple of times and we are considering adding.
In your diagram are "Use case" boxes the same as Requirements?
Should a dependency chart only show features that are part of the dependency graph and ignore features that are not related?
Regards, Chris.