Derived team dependency graph
Team↔team dependencies are derived, never stored — two teams depend on each other when they own systems impacted by the same project. v1 scope: in-flight projects only. Explicit milestone/project dependencies are deliberately not on this graph — see a project detail view.
Legend
team node / derived team↔team dependency (animated)
system node, dashed line = ownership
Click a blue edge to see the shared projects and systems behind the dependency.
Derived dependencies (4)
- Payments ↔ Identity
- Identity ↔ Mobile
- Payments ↔ Mobile
- Payments ↔ Data Platform