4 min leitura • Guide 440 of 877
How to Manage Cross-Team Dependencies in Development?
How to manage cross-team dependencies in development?
Manage cross-team dependencies by creating dependency tasks that link teams, using labels to identify external dependencies (dep:team-api, dep:team-platform), establishing regular sync meetings, documenting dependencies in NoteVault, and escalating blockers quickly. Assign an owner per dependency to drive resolution.
Cross-team dependency labels
| Label | Purpose |
|---|---|
| dep:external | External team dependency |
| dep:team-api | API team dependency |
| dep:team-platform | Platform team dependency |
| dep:team-mobile | Mobile team dependency |
| blocked:external | Blocked by external team |
| needs:api | Needs API from another team |
| needs:design | Needs design from design team |
Dependency task template
## Dependency: [Feature] needs [Team] API
### Teams Involved
- Requesting: Frontend Team
- Providing: API Team
### Dependency
- What: User preferences API endpoints
- Why: Frontend feature requires new data
- When needed: Sprint 6
### API Contract
GET /api/v1/users/{id}/preferences Response: { theme: string, notifications: boolean }
### Status
- [x] Contract agreed
- [x] API team scheduled work
- [ ] API implemented
- [ ] API in staging
- [ ] Frontend integrated
### Communication
- Slack: #team-sync
- Owner: @api-lead
- Escalation: @engineering-manager
### Risks
- API team has competing priorities
- Contract may need changes
Cross-team dependency workflow:
- Identify dependency - During planning or design
- Document early - Create dependency task
- Agree on contract - Interface definition
- Schedule work - Both teams plan
- Track progress - Regular check-ins
- Integrate - When dependency delivered
- Verify - End-to-end testing
- Close - Both teams confirm done
NoteVault dependency tracking
# Cross-Team Dependencies
## Active Dependencies
### Frontend → API Team
| Feature | Contract | Status | Due |
|---------|----------|--------|-----|
| User prefs | Agreed | In Dev | Sprint 6 |
| Export API | Draft | Planning | Sprint 7 |
### Mobile → Platform Team
| Feature | Contract | Status | Due |
|---------|----------|--------|-----|
| Push notifications | Agreed | Done | Sprint 5 |
| Offline sync | Draft | Discussion | Sprint 8 |
## Dependency Contacts
| Team | Primary | Escalation |
|------|---------|------------|
| API | @api-lead | @eng-manager |
| Platform | @platform-lead | @eng-manager |
| Mobile | @mobile-lead | @eng-manager |
| Design | @design-lead | @product-head |
## Sync Meetings
- Cross-team standup: Tuesday 10am
- Dependency review: Thursday 2pm
Reducing cross-team dependencies
| Strategy | How |
|---|---|
| Interface contracts | Define APIs early |
| Decoupled architecture | Reduce tight coupling |
| Self-service platforms | Reduce requests |
| Full-stack teams | Reduce handoffs |
| API versioning | Allow independent progress |
| Feature flags | Deploy independently |
Escalation process
| Blocker Age | Action |
|---|---|
| 1 day | Direct conversation with dependency owner |
| 3 days | Escalate to team leads |
| 1 week | Escalate to managers |
| 2 weeks | Escalate to directors |