Advanced Roadmaps for Jira: Portfolio-Level Reporting, Scheduling, Planning

Atlassian Jira is the premier work management tool on the market. Their strength lies in the myriad of deployable configurations and customizations to support the way your business works versus adapting to the tool.

One major challenge across a variety of businesses, large and small, is continual portfolio and project management on Jira.

All of my teams are successfully working in Jira,” our clients tell us, “but I need the ability to capacity-plan, forecast, and schedule across my entire project portfolio — at the 10,000 ft level.”

Oxalis.io has spent over 4 years managing portfolios, evaluating Project Portfolio Management (PPM) software, and consulting with companies on these challenges. We are award-winning experts, and can help you solve this problem one time, the right way.


Our Recommendation

Our Atlassian Marketplace app recommendation: Advanced Roadmaps for Jira.

For those on Jira Cloud, this is included with the Premium Cloud offering (see our Jira Buyers Guide for more details). For Server and Data Center licensed customers, this is offered as an add-on with the following pricing:

Number of UsersServerNumber of UsersData Center
1-10$101-50$1,600
11-25$1,43051-100$3,000
26-50$2,620101-250$6,000
51-100$4,750251-500$8,000
101-250$9,490501-750$12,000
251-500$14,240751-1,000$12,000
501-2,000$18,9201,001-2,000$14,000
2,001-10,000$24,7402,001-3,000$15,000
10,000+$30,5603,001-4,000*$16,000

There are many tools out there attempting to solve this problem—none of which are remarkable, and none of which work as well with Jira.

Now, like any tool or Jira app, simply installing and enabling Advanced Roadmaps for Jira is not enough for full functionality.

Step 1: Prepare your data

First things first: Establish how you want to structure and measure your teams progress, estimates and organization structure.

This translates directly to:

  1. Will your plan show multiple projects, a singular project, or a program? We’ve successfully modeled Advanced Roadmaps around a single Jira project, tracking a portfolio of activity. You must first define the components of your projects, whether product based or activity based. Define your unit of measure of estimation and projects (story points vs. days vs hours, etc)—common definition is important here to represent on a single plan.
  2. Define how your team delivers. Are you a singular product team, a quality assurance (QA) team, or a team of consultants? This will define how you assign, analyze, and measure your team’s tasks, resource needs, and capacity. Do you want to know if you need to hire more QA Analysts? Project Managers? Do you want to know if you need to establish a new scrum team with integrated skillsets? These questions dictate your structure and you may need to establish a bit of organization planning beforehand.

    By the way, Oxalis can help you with that.

  3. Define the hierarchy. Hierarchy of issue types is important here. Make sure you rationalize the parent/child relationships between your issue types. This dictates nested viewing functionality in the plan and will pay dividends in your organizational future.

The standard issue type flow is:

Epic > Story > Sub-Task.

It could easily be

Epic (Defined as the Customer) > Project > Task/Milestone/Deliverable > Sub-Task.

You may also add levels above Epic to represent even broader summations of work.

Jira Hierarchy Example
An example of a Enterprise-level hierarchical structure built on top of Advanced Roadmaps

We included Sub-Tasks in this hierarchy for a reason: Sub-Tasks are easy to enter (speed of entry is important to teams), can be nested easily in the plan, and have all the same inherent functionality as a Task or Story in Jira. If you have a Sub-Task of any size, and they are not related to multiple tasks or stories simultaneously, include them in your structure to resource directly against them.

Key Note: Advanced Roadmaps for Jira is a team-based capacity model. For those of you looking for individual resource forecasting and capacity management, send us a message and we’ll explore the best path forward to get this data in the system as a more targeted report format..

Step 2: Import your data to a plan

The next step is to create the Advanced Roadmap. You follow a wizard-like interface and select a couple different source types for your plan:

  • Select a singular project, board, or filter for the plan.
  • Select multiple sources for your plan (see Step 1 for important preparation considerations)
A Gantt Chart on Advance Roadmaps for Jira
A Gantt Chart on Advance Roadmaps for Jira

Key Note: We recommend including more on this step rather than less. Advanced Roadmaps allows you to filter your plan view to your liking to concentrate on key bodies of work anyways. Filtering is easier than constantly updating your data sources.

Make sure to consider what type of data to display. Do you want Epics displayed? What is the definition of “Epic” at your organization? Will you need an additional issue type – one step higher to properly capture the scope of your work?

At Oxalis, we use Epics to our clients and stories to track the projects associated with each of those clients. If you use Epics in the more traditional Agile sense of a large user story that spans multiple sprints, perhaps consider creating a rollup issue type to represent products, initiatives, or big features (or all three!).

Key Note: Advanced Roadmaps, like much of Jira, allows you to define custom issue types for display on the roadmap – such as Initiative or Feature. If that definition is more to your liking, then this initiative or Feature can be added to the hierarchy of data to encompass multiple epics, etc.

Step 3: Utilize your plan

Now that data is set up and loaded, you are onto plan usage. Remember that you can change the plan on the fly anytime. It is a sandbox model, meaning that you can play around to your heart’s content without committing the data to live projects until ready to do so. You review the changes and save all or selected items back down to the live records.

One big feature we should mention is scenario planning. You can create more than one plan and select the best scenario for your organization after resourcing and scheduling.

Pros and Key Features of Advanced Roadmaps for Jira:

  • Sandboxing: Quickly update key project details. Click + drag the timeline, update the story point estimate, or even create a new issue – all directly from the Advanced Roadmaps plan view. Commit the changes you want to keep and discard the rest.
  • Dependency Tracking + Alerting: Advanced Roadmaps will alert you if a team is booked over the assigned capacity or if a project is past its end date yet still in progress.
  • Visual Hierarchy and Rollup of Data: Advanced Roadmaps allows you to view your entire portfolio at-a-glance, or drill down to the Sub-Task quickly and efficiently. It will even summarize progress , in terms of points, issue counts, or days:
A breakdown example of progress

Cons of Advanced Roadmaps for Jira:

  • Inability to perform user-level capacity planning. In the current version (3.29.1), Advanced Roadmaps is limited to team-level capacity planning.

Recommended Readings and where to get help:

Ready for a Jira Advanced Roadmaps quote or to learn more information?

Fill out the form below and an Oxalis team member will be in touch shortly.

GET THE CONVERSATION STARTED!

Feel free to send us a message in the form below. We’re very approachable and would like to talk more about how we can meet your needs: