Dependencies and Relationships

Overview

Dependencies encode sequencing across requirements and tasks.

They expose blockers early and protect delivery planning.

Key Concepts

• Blocks / Blocked by: sequencing relationship
• Related: association without sequencing intent
• Dependency chain: multi-hop set of dependencies
• Blocked item: item that cannot progress due to a dependency

How It’s Used

Use dependencies during planning and execution.

Use them for “blocked work” triage during weekly reviews.

Benefits

• Clear sequencing for delivery work
• Earlier visibility into blocker risk
• Cleaner reporting for critical path work

Setup Steps

1

Create a dependency

Create a dependency from an item detail view.

Related: Creating Dependencies Between Requirements

2

Review dependency chains

Review upstream blockers and downstream impacts.

Related: Viewing Dependency Chains

3

Manage blocked items

Create a repeatable blocked-items view for governance reviews.

Related: Managing Blocked Items

Best Practices

• Prefer dependencies for true sequencing constraints.
• Avoid circular dependencies.
• Record unblock conditions in comments.

Summary

Dependencies make planning explicit.

They also create a shared language for blockers and sequencing.