/
Dependency-Aware Planning & Critical Path: How It Works

Try Advanced Release Planning for Jira Cloud free for 30 days

Dependency-Aware Planning & Critical Path: How It Works

This page explains how Release Management, Roadmaps & Product Portfolio for Jira treats cross-team dependencies as a live risk to a committed release date — not just a static map drawn at planning. It is a factual companion to the article The Dependency Nobody Flagged: Keeping a Committed Release Date Honest Across Teams and to The three things that erode a committed release date.

A confidence vote is a snapshot. So is a dependency map drawn on PI planning day. Release Management, Roadmaps & Product Portfolio keeps that map current by treating dependencies as a live input to the Monte Carlo forecast, not a diagram reviewed once and filed away.

Hard links vs. soft links

  • Hard link — the dependent work item literally cannot start until the blocking item is done. A negative-slack hard link sitting on the critical path delays the committed date directly.

  • Soft link — a sequencing preference or convenience. Soft links carry lower risk and do not drive the critical path.

The app distinguishes the two so teams stop treating every link with the same urgency — and stop discovering, in week six, that a link filed as "soft" was actually load-bearing.

What it looks like in the app

Capability

What it does

Capability

What it does

Dependency-aware Monte Carlo forecasting

The forecast accounts for critical-path slack; negative slack on a blocking chain pushes the probable completion date later.

Critical Path view

Shows the exact ordered sequence of work currently dictating the committed date, as a ribbon.

Cross-release context nodes

Blockers living in a different Fix Version — often owned by another team — appear directly in the path instead of staying invisible until a status meeting.

Cycle detection

Circular dependencies are detected, flagged, and excluded from the path calculation rather than silently distorting it.

Ranked risk heatmap

Items on or near the critical path are sorted by risk score, surfacing the one dependency worth a conversation this week.

Shipped in Version 2.6.0 — see the release notes.

How to act on the signal

  • Reclassify a soft link as hard the moment its owner confirms a real blocking relationship — don't wait for the retro to find out.

  • Resequence work while slack still exists on the critical path, not after it's gone.

  • Bring the Critical Path view into a cross-team sync so the team holding the risk is in the room that decides how to resequence it.

Related