Project portfolio management in Jira

Jira project portfolio management means planning, tracking and governing many projects at once inside Jira. This guide covers what Plans does, what roadmap apps add, and what the people funding the portfolio need to see.

7
min read
Jira project portfolio management is the practice of planning, tracking and governing many projects at once inside Jira, so an organisation can see where its delivery capacity is going and decide whether each project still deserves its funding.

Jira project portfolio management is the practice of planning, tracking and governing many projects at once inside Jira. A single Jira project answers for its own backlog. A portfolio answers for the money, so it has to show where delivery capacity is going and whether each project still deserves its funding.

Jira began as an issue tracker for one team's work. It still does that job well. Everything portfolio-shaped arrived later, in layers. If portfolio management has landed on your desk, because you lead the PMO or because you own Jira and the CFO wants to know what the licences produce, you are choosing across three layers. Jira ships the first natively, Marketplace roadmap apps add the second, and the third is the governance view the people funding the work rely on.

What native Jira covers for portfolio work

Start with what you already pay for. Every Jira project gives a team a backlog and a board. Dashboards and saved filters let you assemble cross-project views by hand, and JQL slices work items any way you like. For a small portfolio, a dashboard of filter gadgets is a legitimate answer. Some PMOs run on exactly that.

The purpose-built layer is Plans, previously called Advanced Roadmaps, which Atlassian includes in Jira Premium and Enterprise. Plans pulls work items from many projects and boards into one timeline, models dependencies between them, adds hierarchy above the epic and sketches capacity against teams and sprints. It also supports scenarios, so you can test a reshuffle before you commit to it. For the scheduling half of portfolio management (what is happening, in what order, blocked by what), Plans is a serious tool.

Plans holds the delivery schedule. It records when epics start and finish. It has no native place for what a project has cost against its budget, the risks it carries or the decisions behind a change of scope.

What roadmap apps add on top of Plans

The Atlassian Marketplace has a mature category of portfolio and roadmap apps that extend the same scheduling layer. They add richer cross-project timelines and Gantt views, and capacity planning down to the individual. Some also bring portfolio views to Jira tiers that don't include Plans.

These apps answer delivery questions at portfolio scale, such as who is working on what and where dependencies collide. If the roadmap no longer fits on one screen, they fix that. Like Plans, their unit of interest is a piece of work with its dates, and the project's budget and baseline sit outside that frame.

What the portfolio board needs to see

Portfolio management exists because someone is paying for the portfolio, and the people paying ask different questions from the people delivering. Delivery tooling answers whether the team is shipping. The funding side brings three questions of its own.

  • Is each project where it said it would be? Every project starts with a budget and a set of dates. At every review, the board needs cost, schedule and scope read against that baseline.
  • Is it still worth the money? Estimates and scope move, so a project that made sense at the start can stop making sense six months in. Someone has to check at each steering committee, with the numbers in front of them, and have the standing to call a stop.
  • What has changed, and who agreed to it? Scope changes, risks and decisions pile up between meetings. The board needs the record, so each review starts from what was agreed last time.

To answer them, the board needs the same few things for every project, each read against its baseline. It needs status on cost, schedule and scope, the open risks, the decisions made and the decisions due, and the date of the next review. Across the portfolio, it needs to see which projects have drifted, so the meeting spends its time on those.

A project can be green on every delivery measure and still be in trouble with the people paying for it. The team ships, the sprints are healthy and the timeline holds, while spend has run ahead of the work done for two quarters. Delivery reports can't show that. That gap is why portfolio governance is a separate discipline from delivery management.

The governance record Jira doesn't hold

Jira has nowhere native to keep the answers to those questions, so they end up outside it. The budget lives in a spreadsheet and the risks in a document. Decisions sit in meeting minutes nobody can find, and scope changes in an email thread.

The delivery record in Jira is thorough. Jira timestamps and attributes every status change and estimate revision. The governance record depends on memory. When an auditor or a new CFO asks who agreed to a scope change and what it did to the budget, someone goes digging through old decks. Plans isn't designed to hold this record. A tool built only for scheduling won't hold it either.

How portfolio management works when delivery runs in Jira

A portfolio in Jira is a set of projects that someone has to govern together. Plans or a roadmap app groups them for scheduling. The governance view needs the same grouping, plus the numbers and the decision record the schedule doesn't carry.

That view works best as a layer above the boards. Each project gets a plan of work packages with budgets and dates, set once as the baseline. A project manager links whichever Jira work items deliver each package, so teams keep their own issue types and hierarchy. The project manager records progress on each package as the work moves. The portfolio view then rolls the projects up. The board sees each project's position against its baseline, and nobody builds a pack.

Keep the two layers apart. Plans or the roadmap app owns the schedule and capacity. The governance layer owns the baseline and the record of decisions and changes against it. Both read the same Jira work, so neither needs a second copy of it.

How Tollgate shows the portfolio as a dashboard

Tollgate is a project and portfolio dashboard for Jira Cloud, built by Softwired as a Forge app. Each Jira project gets a dashboard, a plan and three registers, and the steering committee reads the dashboard in place of a deck.

  • Dashboard. The project's overall status and key message, the project brief, and Cost, Schedule and Scope cards that show the status you set beside the one Tollgate calculates.
  • Plan. Work packages with dates, budget, actual, forecast and percentage complete, a timeline, and an S-curve that tracks earned value or schedule progress.
  • Registers. Work packages, risks (and opportunities) and decisions (and changes), kept under the same project as the dashboard, so the answer to a follow-up question is one click away.
  • Portfolio. Tollgate Portfolio rolls up every project in a Jira Plan, so the portfolio board sees every project in one place.
  • Status report. A two-page A4 landscape PDF for anyone who isn't in the room.

Tollgate sits beside Plans or your roadmap app. Keep those for the schedule. Use Tollgate for progress against the plan and for the steering committee view. Work packages live in Tollgate, linked to the Jira work items that deliver them.

Ask Tollgate answers questions about the data through Rovo, and it needs Jira Premium or Enterprise. Because Tollgate runs on Forge, the data stays in your Atlassian tenant.

Questions about Jira project portfolio management

Does Jira have portfolio management built in?

Plans comes with the Premium and Enterprise tiers and covers timelines across projects, plus capacity. Free and Standard don't include Plans, so teams on those tiers use dashboards and filters or a Marketplace app. On any tier, native Jira has no built-in place for budget against a baseline or a record of decisions and scope changes.

What is the difference between Jira Plans and a portfolio dashboard?

Plans schedules work across teams. A portfolio dashboard reports how each project stands against its baseline, including cost and scope, for the people funding it. The two can run on the same Jira site.

How does Tollgate roll projects up into a portfolio?

Tollgate Portfolio is a page under Jira's Apps menu. Choose a Jira Plan and it lists every project in that plan, one row per project, with health, budget against forecast and the variance, worst first. Each row reads the dashboard its project manager keeps current, so there is no second set of numbers. The portfolio needs Jira Plans, which comes with Premium and Enterprise.

Where do risks and decisions fit?

Each project keeps its risks (and opportunities) and its decisions (and changes) in registers beside the plan. The steering committee sees what was decided, by whom and when, next to the cost and schedule figures it affected.

Does Tollgate need a particular Jira setup?

Tollgate holds the work packages, and you link any Jira work item to them, so epics, stories and tasks all work. Tollgate doesn't require new issue types or a new hierarchy.

What does Tollgate cost?

On a Jira site with 10 users or fewer, Tollgate costs nothing. Larger sites can try it at no cost during the Marketplace trial. After that the price is per user, and Atlassian adds it to your existing invoice each month, on the same user tier as Jira. The full breakdown is on the pricing page.

Try it on one live project

Install Tollgate from the Atlassian Marketplace, then set up one live project and add the rest of the portfolio once the dashboard has earned its place at the steering committee. It's free on Jira sites with up to 10 users. Larger sites get a free trial through the Marketplace, and Atlassian bills against your Jira user tier only if you keep it. Your Atlassian admin can cancel it at any time. You can also book a 30-minute demo on a real project.

See the method running in Jira

Your steering committee reads each project live in Jira: the dashboard, the work-package plan and S-curve, and the risk and decision registers.