Task Dependencies

Overview

Task dependencies encode sequencing constraints across execution work.

They protect planning and reduce surprise blockers.

Key Concepts

• Blocks: upstream task must complete first
• Blocked by: current task cannot start yet
• Related: association without sequencing intent

How It’s Used

Use dependencies during sprint or phase planning.

Use them during blocker triage.

Benefits

• Clear sequencing for execution work
• Faster identification of prerequisite work
• Cleaner “blocked” reporting signals

Setup Steps

1

Add a dependency

1. Open a task.
2. Locate the Dependencies area.
3. Select Add dependency.
4. Select the related task and relationship type.

2

Validate sequencing intent

1. Confirm the dependency represents a true constraint.
2. Remove dependencies that are only “related context”.

3

Review for cycles

1. Scan for circular dependencies.
2. Remove or re-sequence relationships when a cycle exists.

Best Practices

• Keep dependencies minimal.
• Use comments to document why a dependency exists.
• Pair dependency review with blocked-item review.

Summary

Dependencies should represent real sequencing constraints.

They should not replace links or references for general context.