Dependencies & Integration

Manage interfaces, cross-team commitments and end-to-end delivery.

• Another team says our dependency is not their priority. What should we do?Unagreed external dependency
• Our integration works in isolation but fails end to end. Why?Local completion without system verification
• We discovered a dependency late in the project. How do we assess it?Hidden dependency
• Two teams each wait for the other to finish. How do we break the loop?Circular dependency
• A shared API changes without notice. What should happen?Uncontrolled interface change
• How do we define a dependency so it can be managed?Vague dependency record
• The supplier says ready, but our team cannot use the output. What is missing?Readiness definition mismatch
• How do we coordinate cutover tasks across several teams?Unintegrated cutover sequence
• Our dependency dates keep changing. How do we protect the project?Volatile external readiness
• Integration has no single owner. Who should coordinate it?Unowned integrated outcome
• The same data means different things in connected systems. How do we resolve it?Semantic data mismatch
• Can we use a mock to unblock a dependency?Controlled provisional interface
• Our project depends on an external approval date we cannot control. What should we do?External decision uncertainty
• How do we manage dependencies between business and technical work?Cross-discipline handoff gap
• A dependency is complete, but the receiving team was not told. How do we prevent this?Unconfirmed handoff
• Our integration tests use unrealistic data. What should we improve?Unrepresentative integration evidence
• How do we track dependencies without building an unreadable chart?Dependency information overload
• A shared environment is unavailable during our test window. What are the options?Environment capacity conflict
• How do we prevent interface changes during final testing?Interface stabilization gap
• What should happen when a dependency is no longer needed?Stale dependency commitment