Eleven rows in the dependency tracker. Owner, needed-by date, status, a red-amber-green dot. At the Thursday sync the program manager reads down the column: eight closed, two amber, one green. The committed release date is 9 June and the confidence vote came in at four fingers. Nobody has a reason to raise a hand.
Three weeks later the release is nine days late. The tracker was current every single week. It was just answering a different question.
What dependency tracking records
Dependency tracking is the habit of keeping every cross-team or external dependency in one place with an owner, a needed-by date and a status, then reviewing it on a rhythm. It lives in a spreadsheet, a board column, a Confluence table or a Jira filter on blocked work. (Search for the same phrase and you will also find tools that track software package dependencies in code. This article is about the delivery kind: work that cannot finish until other work does.)
It is worth doing. The list is the team’s expert engineering judgment about what the release leans on, written down where everyone can see it, and it feeds the confidence vote directly. A tracker with named owners also changes behavior: people answer a question faster when their name is next to it.
A status column is not a date
A tracker answers “is this dependency open or closed, and is it on time?” The committed date needs a different answer: “given everything still open, where does the release land?” Between the two sit three gaps:
- Status is per row, the date is per release. Three amber rows can be harmless or fatal. It depends on whether they sit on the chain of work that is dictating the date.
- Late rows arrive late. A dependency that was not on the list on planning day is invisible until someone adds it. By then the vote has been taken without it.
- A slip is a color change, not a number. Green to amber says “watch this.” It does not say the 85% forecast just moved five days.
This is the second of the three things that erode a committed release date: dependencies surfaced too late, or surfaced on time and never priced. Scope creep and capacity changes are the other two, and they rarely arrive alone.
Keep the tracker. Read the gap in days.
The team owns the assumptions: which dependencies are real, which are only preferences, who owes what by when. Keep that judgment. Then connect it to the forecast so it stays current.
- Record each tracker row as a Jira issue link between the actual work items, including blockers in another team’s Fix Version.
- Mark each link hard or soft. Hard if the work cannot start without it, soft if it is a sequencing preference. Reclassify when you learn more.
- Give outside gates a placeholder. For a vendor drop or a sign-off with no Jira issue, create a placeholder work item with the promised date and a named owner, and hard-link it. When the promise moves, update the date.
- Read one number at every sync: the gap in days between the committed date and the forecast at the confidence the team committed at.
An illustration, not customer data. The release is committed for 9 June at 85% confidence. At the vote the 85% forecast sat at 4 June: five days of margin. In week four a vendor SDK that gates the payments work slips by two sprints. The tracker row turns from green to amber. The 85% forecast moves to 12 June, three days past the commitment, while the 50% forecast is 8 June, still inside it. The release reads attention, not yet at risk, and the team still has room to act.
Now the sync has a decision with a number on it. Escalate to the vendor? Ship payments behind a flag and follow up? Renegotiate the date this week? Each is still the team’s call, and so is every assumption behind the forecast. What changes is that the call happens in week four, not week nine.
Where Advanced Release Planning fits
Advanced Release Planning for Jira reads the dependencies you record as Jira issue links. It does not import a tracker or keep a status column of its own, and it does not put a number of days on an individual row. Hard links feed a dependency-aware Monte Carlo forecast built on the team’s actual throughput. The Critical Path view shows the ordered sequence of work currently dictating the committed date, cross-release context nodes bring in blockers from another team’s Fix Version, and a ranked risk heatmap sorts the items on or near that path. The committed date carries its confidence band (50%, 85%, 95%) and stays current as scope, dependencies and capacity move. The team sets the assumptions: which throughput window, whose capacity, what is in scope. The app does the arithmetic at Monte Carlo scale and keeps it live. Status reads on-track at or above P85, attention between P50 and P85, and at-risk below P50.
For how Jira links carry the relationship, read why Jira issue links say what blocks what but not what it costs the date, and how project dependencies get typed at planning and priced too late. For the step-by-step handling of hard links, soft links and external placeholders, see the dependency-aware planning reference doc.
Key takeaways
- A dependency tracker captures the team’s judgment about what the release leans on. Keep it, and keep it in the vote.
- Status is per row. The committed date is per release. A color change does not tell you what moved.
- Record each row as a hard or soft Jira issue link, and give outside gates a dated placeholder.
- Read the gap in days at the committed confidence at every sync, and renegotiate before the slip.
FAQ
What is dependency tracking in project management?
Keeping a list of the dependencies a release relies on, each with an owner, a needed-by date and a status, and reviewing it on a regular cadence.
What should a dependency tracker include?
The blocking and blocked work, both owners, the needed-by date, whether the dependency is a hard gate or a preference, and a link to the real work item. Add the release-level gap in days so the list says what the open rows cost the date.
How do you track dependencies in Jira?
Record them as issue links between work items, mark them hard or soft, use a placeholder work item for outside gates, and read the committed date against the live forecast at each sync.
Keep your dependency tracker. Add the number it’s missing. See every open dependency priced against the committed date in Advanced Release Planning, or start a free trial on the Atlassian Marketplace.




Leave a Reply
Your email is safe with us.