Creating Dependencies Between Requirements

Overview

Requirement dependencies capture sequencing across scope statements.

They prevent downstream work from starting too early.

Key Concepts

• Upstream requirement: prerequisite scope
• Downstream requirement: dependent scope
• Blocks / Blocked by: sequencing relationship used for planning

How It’s Used

Use dependencies during discovery and design sequencing.

Use them to communicate prerequisite decisions.

Benefits

• Cleaner sequencing and planning
• Earlier identification of blocker risk
• Clearer discussion during governance reviews

Setup Steps

1

Open the requirement

1. Navigate to Requirements.
2. Open the downstream requirement.

2

Add a dependency

1. Locate the Dependencies area.
2. Select Add dependency.
3. Choose the upstream requirement.
4. Select relationship type, such as Blocked by.

3

Confirm the relationship

1. Confirm the dependency appears on both requirements.
2. Add a comment describing the unblock condition.

Best Practices

• Keep dependencies minimal and meaningful.
• Use comments to document why the dependency exists.
• Review dependencies during requirement approval.

Summary

Dependencies encode prerequisite scope.

They also reduce rework caused by premature execution.