Dependencies exist in every project and initiative. Between teams, initiatives, deliverables—you name it: the combinations and levels of complexity are endless. That’s why we’re bringing you a way to identify highly dependent items early in the planning stage.
By creating relationships and highlighting these risks earlier, you can be sure that your team is clear on what needs to be done, who is doing what, and what needs to be finished. Your time is precious, and we know that.
Our Dependencies feature makes roadmapping more efficient by reducing the number of updates required, even when dependencies are linked across different roadmaps.
Let’s get into some examples of how Dependencies can help increase clarity by helping you see which items are dependent across your team’s roadmaps.
See the big picture—even across different roadmaps
Our Dependencies feature lets you link an item to any other item, even if it exists on someone else’s roadmap.
When you hover over items with added Dependencies in the Timeline view, you can see what items or key dates are linked to each other. Take it one step further and roll all your team’s roadmaps into a Master roadmap to see a high-level view of all your Dependencies.
In the Items Table and in Swimlane view, you can see these Dependencies represented as badges next to items, which indicate the number of Dependencies linked to that item. This is a great way to highlight items that have a lot of Dependencies on them.
Keep your team aligned when dates change
Use the Moves With Dependency for better alignment.
The Moves With option is great for moving the dates of dependent items, all with just one click.
Here’s a scenario to give you an idea of what Moves With can do for alignment:
Say your design team gets hit with a delay and they need a few more days to complete some mocks. Development, QA, Marketing and Sales will need to know about that snag. With our Moves With Dependencies, all it takes is one click-and-drag of the item across the timeline for the dependent item to follow in parallel. Those teams then get pinged that a change took place (via email and in-app notifications), and the dates on their items get updated before anyone can say, “Wait, weren’t these mockups due yesterday?!”
That’s also one less meeting and four fewer roadmap updates—saving you time.
Use Blocked By/Is Blocking to communicate a relationship between two items, where one item cannot move before or after the other. You can use this to block specific teams or blackout periods, for example.
Blocked by/Is Blocking Dependencies automatically maintain a neat visual system between a complex set of tasks that need to happen in a certain order. Here’s an example:
The product team is working on a Slack integration feature. Great! But that means there are many cross-team initiatives that need to be completed beforehand. These earlier initiatives have to be visualized in a way that shows this timely relationship. This is where a Blocking Dependency becomes super useful.
You can also check an item’s dependency changes on the activity card. There you’ll see a record of how many times something got delayed and by what.
Share Dependencies outside of Roadmunk
Provide visibility to the rest of your stakeholders by exporting your roadmap as a PNG, HTML file or by publishing it to a URL. During export, you can choose whether Dependency lines are shown or not.
On a shared roadmap, items with Dependencies are linked with lines that show there’s a relationship there. To see the difference between the two types of Dependencies, simply click on an item card and it’ll show you exactly what’s what.
For step-by-step instructions about our Dependencies solution, check out these articles.
Click here to explore our Dependencies feature for yourself. Happy roadmapping!
P.S. Join us for a webinar on March 21st for a demo on Dependencies and bring your questions (big or small) for a live Q&A. No worries if you can’t make it, we’ll send you the recording after it’s over.