Skip to main content

Dependency List Reports

Dependency list reports display open upstream and downstream dependencies, helping teams identify and manage work item relationships that impact delivery.

Understanding Dependencies​

Dependencies represent relationships between work items where one item relies on another to be completed first. Managing dependencies is critical for:

  • Release planning and scheduling
  • Risk identification and mitigation
  • Cross-team coordination
  • Program-level visibility

Available Reports​

Open Backlog Dependency List Report​

Shows a list of open downstream and upstream dependencies for backlog items (stories, defects, tasks) in a project or release.

Use this report when you need to:

  • Identify backlog items blocked by other work
  • Track dependencies within a release or project
  • Coordinate work across teams at the story level
  • Plan sprint commitments considering dependencies

Open Backlog Dependency List

Open Portfolio Item Dependency List Report​

Shows a list of open downstream and upstream portfolio item dependencies (epics, features, capabilities) in a project or release.

Use this report when you need to:

  • Identify portfolio items blocked by other initiatives
  • Track strategic dependencies across programs
  • Coordinate work at the portfolio level
  • Plan roadmaps considering cross-portfolio dependencies

Note: This information is also available visually on the Portfolio Item Dependency Report.

Accessing Dependency List Reports​

Backlog Dependency List​

  1. Click the hamburger menu Hamburger icon > Reports > All Reports.
  2. In the Project or Release Reports section, click Open Backlog Dependency List.
  3. Select from the available filters and click Go.
  4. To clear filters, click Reset.

Portfolio Item Dependency List​

  1. Click the hamburger menu Hamburger icon > Reports > All Reports.
  2. In the Planning Reports section, click Open Portfolio Item Dependency List.
  3. Select from the available filters (optional) and click Go.
  4. To clear filters, click Reset.

Report Filters​

Both reports support standard filtering options to narrow the dependency view:

Project / Release Filter

  • Limits dependencies to specific projects or releases
  • Helps focus on relevant delivery timeframes

Team Filter

  • Shows dependencies for specific teams
  • Useful in multi-team environments

Status Filter

  • Filters by dependency status (open, closed, blocked)
  • Focus on active dependencies requiring attention

Date Range Filter

  • Shows dependencies within specific timeframes
  • Helps with release planning

Understanding the Report Output​

Columns Displayed​

Dependency Type

  • Upstream: Work items this item depends on (blockers)
  • Downstream: Work items that depend on this item

Source Item

  • The work item with the dependency relationship
  • Click to view item details

Target Item

  • The related work item in the dependency
  • Click to view item details

Status

  • Current status of both items in the dependency
  • Helps identify if blocking items are progressing

Owner / Team

  • Who is responsible for each item
  • Facilitates cross-team coordination

Target Date

  • Planned completion dates
  • Highlights schedule risks

Using Dependency Reports Effectively​

Sprint Planning​

  1. Review backlog dependency list before sprint planning
  2. Identify stories blocked by external dependencies
  3. Coordinate with other teams to resolve blockers
  4. Consider dependency completion dates when committing to sprints

Release Planning​

  1. Review portfolio item dependency list during PI planning
  2. Identify features dependent on external work
  3. Sequence releases based on dependency relationships
  4. Communicate cross-program dependencies to stakeholders

Risk Management​

  1. Monitor open dependencies as potential risks
  2. Track aging dependencies that haven't closed
  3. Escalate dependencies blocking critical work
  4. Plan mitigation strategies for risky dependencies

Cross-Team Coordination​

  1. Export dependency reports for program sync meetings
  2. Share reports with dependent teams
  3. Use as agenda for dependency resolution discussions
  4. Track coordination effectiveness over time

Dependency Management Best Practices​

Creating Dependencies​

  1. Be specific: Clearly define what one item depends on in another
  2. Document context: Add notes explaining why the dependency exists
  3. Set target dates: Establish when the blocking item needs completion
  4. Assign owners: Ensure both items have clear ownership

Monitoring Dependencies​

  1. Review regularly: Check dependency reports weekly or during standups
  2. Update status: Keep dependency status current as work progresses
  3. Escalate blocks: Raise visibility on dependencies causing delays
  4. Close promptly: Mark dependencies resolved when blocking work completes

Reducing Dependencies​

  1. Challenge necessity: Question if dependencies are truly required
  2. Refactor work: Break down items to reduce coupling
  3. Parallelize when possible: Structure work to enable concurrent progress
  4. Build interfaces early: Create contracts between dependent items

Communicating Dependencies​

  1. Visualize: Use dependency reports in team and program ceremonies
  2. Be transparent: Share dependency status openly
  3. Coordinate proactively: Don't wait for dependencies to become blockers
  4. Follow up: Track resolution of identified dependencies

Common Dependency Patterns​

Sequential Dependencies​

  • One item must complete before another can start
  • Common in infrastructure or architecture work
  • Requires careful scheduling and buffering

Bi-directional Dependencies​

  • Two items depend on each other
  • Often indicates need for refactoring
  • May require parallel development with clear interfaces

Many-to-One Dependencies​

  • Multiple items depend on a single blocking item
  • High-risk pattern requiring close monitoring
  • Consider prioritizing the blocking item

External Dependencies​

  • Dependencies on items outside your control
  • Require stakeholder management
  • Need contingency planning

Integration with Other Reports​

Dependency reports complement other planning reports:

Troubleshooting Dependencies​

Problem: Too Many Dependencies​

  • Symptom: Teams constantly blocked by external work
  • Solution: Review architecture, increase team autonomy, reduce coupling

Problem: Stale Dependencies​

  • Symptom: Dependencies marked open but blocking work completed
  • Solution: Implement dependency review in team ceremonies, automate closure

Problem: Hidden Dependencies​

  • Symptom: Teams discovering dependencies during execution
  • Solution: Improve planning rigor, conduct dependency mapping exercises

Problem: Cross-Program Dependencies​

  • Symptom: Dependencies across organizational boundaries causing delays
  • Solution: Establish program sync meetings, escalation paths, program-level coordination