Dépendances Tâches Dev | GitScrum

Gérez dépendances tâches pour prévenir blocages et améliorer flux. GitScrum visualise dépendances, identifie travail bloqué et planifie séquence.

4 min de lecture

How to track dependencies between development tasks?

Track dependencies by documenting blockers in task descriptions ("Blocked by: #123"), using blocked labels, creating dependency links in task comments, and reviewing dependencies during planning. Address dependencies early by prioritizing blocking tasks and making dependency chains visible in your board view.

Dependency labels

Label	Purpose
blocked	Task is blocked
blocker	This task blocks others
depends-on:api	Depends on API work
depends-on:design	Depends on design
depends-on:infra	Depends on infrastructure
depends-on:external	External dependency
ready	All dependencies resolved

Task with dependencies

## Feature: User Dashboard

Dependencies:
- [ ] Blocked by: #234 - User API endpoints
- [ ] Blocked by: #235 - Design mockups
- [ ] Blocked by: #236 - Auth service updates

Current status: BLOCKED
Blocked reason: Waiting for API endpoints (#234)

Once unblocked:
- Estimated effort: 5 points
- Assignee: @developer

Notify when #234 completes: @developer

Dependency tracking workflow:

Identify during planning - Document dependencies before sprint

Label appropriately - blocked and blocker tags

Order priority - Blockers before blocked tasks

Daily review - Check blocked status in standup

Unblock proactively - Prioritize blocking work

Update status - Remove blocked when resolved

Start dependent work - Notify assignee

Board with dependency visibility

Column	What to Track
Blocked	Tasks waiting on dependencies
Ready	Dependencies resolved
In Progress	Active work
Review	Completed work
Done	Released

Dependency patterns

Dependency Type	Example	Management
Task-to-task	Feature needs API	Link in description
External	Third-party integration	Label, track separately
Design	UI needs mockups	Cross-team coordination
Infrastructure	Needs new service	DevOps coordination
Approval	Legal/compliance	Track in comments

Daily standup for blocked tasks

Team Standup:

Blocked:
- #245 - User Dashboard (blocked by #234 API - expected today)
- #248 - Payment flow (blocked by external: Stripe review)

Blocking others:
- #234 - User API (in review, blocks 3 tasks)
- Priority: Finish #234 review today

Ready to start:
- #250 - Reporting (was blocked, now unblocked)

Preventing dependency chains

Problem	Prevention
Long chains	Break into smaller tasks
Circular dependencies	Refactor task scope
External blocks	Parallel work available
Design bottleneck	Design ahead one sprint
API bottleneck	Mock APIs for frontend