apex-dependency-mapping

Cross-project dependency mapping identifies and classifies inter-project dependencies across a portfolio to reduce delays. It requires a portfolio data source and stakeholder input to generate a dependency register and network diagrams.

Visualizing circular dependencies is handled through network diagrams and Mermaid diagrams that detect cycles across multiple teams. The mapping process applies risk assessment and remediation guidance to surface these critical paths.

Program increment planning is a core use case for this dependency mapping process. It provides a holistic view of cross-team dependencies to support portfolio planning, risk assessment, and governance.

To start cross-project dependency mapping, run the dependency-mapping command with a portfolio identifier. This generates the initial dependency map and initializes cross-project coordination.

Outputs from cross-project dependency mapping include a dependency register and network diagrams. These artifacts support governance, planning, and cross-project coordination by visualizing critical paths and cycles.

Stakeholder input is required for accurate cross-project dependency mapping. Combining stakeholder knowledge with a portfolio data source ensures the dependency register and visualizations correctly reflect inter-project relationships.