In today's blog post, we will be discussing the multiples of advanced roadmaps: multi-team and organization-level roadmapping, multi-team and organization-level dependency tracking, and multiple scenario planning.
Multi-Team & Organization-Level Roadmapping
From Atlassian: "With Advanced Roadmaps, you can build your roadmap based off of work from as many* Jira boards, projects, and filters as you need. While Advanced Roadmaps will work for a single team, it is particularly well-suited to represent larger pieces of work because it enables you to create additional levels of hierarchy (as many as you need) above the Epic level. So for example, you could map epics from a dozen different teams or Jira projects to a single feature."
It's all about the roll-up! Organizations are often looking for a visual way to answer questions about how teams are tracking toward objectives that encompass multiple Epics. Without Advanced Roadmaps, there is no great way to organize your Jira data for higher-level planning discussions. Whenever you see the term "organization-level roadmapping," think hierarchy. Think, "What at my organization do we plan and track that encompasses many Epics?" Initiative? Yes. Project? Alright. Theme? Yup. Legend? Sure. Some Atlassian customers leverage Advanced Roadmaps for this feature alone. That kind of higher-level organization of the work in Jira is simply that valuable right out of the box!
*There is a limit to how many issues can be pulled into a roadmap.
Multi-Team & Organization-Level Dependency Tracking
From Atlassian: "You can track and visualize dependencies across all of the work in your roadmap, which can be really helpful in accounting for issues that can come up and blockers across your business. The Advanced Roadmap is specifically designed in a way to deal with the number of dependencies across a large body of work."
Dependencies in Advanced Roadmaps are a new way to create and visualize what we Jira users already know as issue links. The dependencies will "call out" problems in the roadmap where new work may not begin until the work it is dependent upon is complete. And by "call out," I mean your roadmap will show warnings. It's nice and visual so you can avoid surprises and adjust your plans for success.
Multiple Scenario Planning
From Atlassian: "Plans change and there's almost always more than one path to getting your project over the line. With Advanced Roadmaps, you can build different versions of a plan in order to account for things like the best- and worst-case scenarios or different strategic options that are available for your organization."
Welcome to the abyss of "what-if" analysis...a blessing and a curse at times! This is a powerful feature for making informed tradeoff decisions when you can't do all the things with all your people in the time you need. For example, let's say a new customer is acquired and now they're the highest priority. This decision means that project work should stop and instead shift to the new client's work, or a new contracted team should be brought on to complete the work. Without Advanced Roadmaps, it is very difficult to visualize this impact. Bonus! Save those visuals for future reference. You know what I'm talking about, those meetings where everyone forgets your past tradeoff decisions and is still wondering why the first project hasn't been delivered yet. If that's never happened to you before, you're the lucky one!