Use cases

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

Portfolio for Jira enables realistic strategic planning; It provides a single source of truth into the current and future health of your initiatives, and what-if scenarios. Portfolio for Jira uses the data in your Jira application instance and displays it on an intuitive interface to help your company efficiently view, plan, and manage initiatives. Teams use Portfolio for Jira to effectively plan by creating reliable forecasts, staying informed with realistic schedules, and effectively troubleshooting and managing releases in an ever-changing environment. 

What's your role?

I'm a Product Manager

As a Product Manager, you need a way to quickly turn the feature ideas and customer feedback into a compelling product roadmap, to keep stakeholders informed, and for your own guidance. You also need to have visibility into the team's progress. If this sounds like you, keep reading to learn about three ways Portfolio for Jira can help you plan better.

Organize your ideas

Start by defining initiatives in Portfolio for Jira; think of initiatives as chunks of work spanning multiple epics and teams, so you can see what needs to be done in the next planning cycle. Once you’ve defined initiatives, they need to be broken down into smaller workpieces to populate the backlog:

  1. Define your initiatives

    Define your initiatives by following the steps provided in Configuring hierarchy levels.

  2. Break down the initiatives into new epics and stories

    Break your initiatives down into epics and stories that are ready for implementation; they can be turned into actual Jira issues.

    Follow the steps provided in Creating and deleting issues in Portfolio.

Build a roadmap

A roadmap is based on scope, time, and people. You can play with these variables in Portfolio for Jira to see different roadmap scenarios. Once you have a backlog of ideas in the form of work items, you need to get everything on a roadmap to share with your stakeholders. These are the three things you need to build a roadmap:

  1. Set the scope

    Once you've organized your ideas and the mental backlog is laid out, the work just needs to be estimated. 

    • Create the strategic focus areas by following the steps provided in Creating and configuring themes.

    • Divide them into smaller projects by following the guidelines provided in the Scope section.

  2. Target release dates

    Configure your release dates by following the steps provided in Creating project-specific releases.

  3. Select your teams

    Define your teams and their velocities in hours or points. The velocity can be linked directly to a board in Jira Software.
    Learn more about resources in Adding and removing teams.

I'm a Dev Manager

As a Development Manager, you’re responsible for making realistic commitments on your team's behalf. During the planning, you need a clear roadmap that you and the product manager have agreed on so you can run the numbers and ensure your team can get it all done. You need a way to easily plan your team's’ resources and see the capacity of the team at any point in time so you have data to show what’s possible and what isn’t. You also want to keep stakeholders informed of progress and status without too much hassle. If this sounds like you, keep reading to learn about three ways Portfolio for Jira helps you plan better.

Master the art of capacity planning

In cases where you have specialized and diverse capabilities in your team, you may want to be more granular with capacity planning to keep your plan realistic and avoid bottlenecks caused by the fact that you need certain skills to complete an item.

Learn more about your team capabilities in Learn Stages & Skills.

See the team capacity on the roadmap

Portfolio for Jira allows you to understand what your team is working on at a much more granular level, so when it comes to planning scope with project and product managers, you have the data to support your views on what’s possible and what isn’t.

  • Capacity view
    The graphical schedule shows both planned capacity and resource utilization. Capacity is displayed as story points for Scrum teams, while capacity is plotted using calendar weeks for Kanban teams. You can view capacity by release, team and even team members.
  • Stories view
    The stories view shows individual stories and their stages of work. When using scrum, the schedule creates a swimlane per team and shows the team’s sprints, as well as the stories scheduled for each of the sprints. When using kanban, the view plots the stories on a day granularity timeline. You can also view the schedule as stories by team person.

    Learn to use the views by following the steps provided in Using the timeline.
Track your projects' progress

In Portfolio for Jira, you can see the progress for individual story items, epics, and initiatives. For anything that is unestimated, you can show those items in relation to items that are estimated. This will allow you to see the percentage of work done on estimated items while also seeing that some unestimated items are still outstanding and require work.

  1. Set your tracking options

    Portfolio for Jira supports different ways to track progress depending on your team's requirements. 
    Learn to configure the progress tracking by following the steps provided in Tracking status and progress of issues.
  2. View your status and progress in the backlog

    The progress and status columns in the backlog allow you to see the progress of your plan items.  

    • Issue Status - Only exists if the backlog item links to one or multiple Jira applications issues. It shows the actual workflow status of these issues. In the case of multiple issue links, an icon is shown for the status of each linked issue. 
    • Progress - Sum of work logs on the linked Jira applications issues, as well as their child elements. 
    Learn to use the views by following the steps provided in Status and progress tracking.

I'm a Project Manager

As a Project Manager, you plan and coordinate work against milestones to make sure you're meeting deadlines, and to show how projects are tracking against business goals. Dependencies are a big thing for you – they account for 90% of your planning-related headaches – so you need to map out these dependencies, and not just track them. Having a graphical or visual presentation of information is really helpful at times.

Plan according to milestones
  1. Set the scope

    Once you've organized your ideas, you can reprioritize the work items.
  2. Define your releases

    Configure your release dates by following the steps provided in Configuring release dates.
Manage dependencies so the timeline is realistic

In Portfolio for Jira, it’s possible to control the sequence in which items are scheduled on the roadmap by setting explicit dependencies.

  1. Create and manage your dependencies
    Configure your release dates by following the steps provided in Managing your scope dependencies.
  2. Configure your hierarchy levels.
    Display the dependencies in the graphical schedule by following the steps given in Configure your hierarchy levels.
Track program toward your goals

In Portfolio for Jira, you can set themes and track progress against them to make sure the organization is executing on strategy and everyone is aligned to the same priorities.

  1. Create your focus areas
    Themes are high-level strategic focus areas, value streams, or investment categories; you can use themes to set priorities and define where your teams should devote most of their time.
    Create and configure your themes by following the steps in Using themes.
  2. Keep track of the progress 
    The graphical schedule shows the results of resource calculations and forecasting based on your plan data. It also provides visibility into forecasted release dates. 
    Track your progress by following the steps provided in Tracking progress and status.

Last modified on Sep 8, 2019

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.