The dependencies heuristic tests whether a value stream can operate independently and achieve fast flow. It exposes hidden dependencies that may block teams or make a candidate modernization slice unsuitable. section 11.3.1
Use a diverse group familiar with different aspects of the value stream to ask:
- Is the subdomain logically independent from other subdomains? section 11.3.1
- Can the team self-serve dependencies from a platform without blocking? section 11.3.1
- Which dependencies are acceptable or unavoidable, and which should be removed by reshaping boundaries, allowing duplication, or moving responsibilities into platforms? section 11.3.1
Treat the heuristic as a first line of defense rather than a complete analysis. Extend it with domain message flow modeling and product-roadmap mapping to uncover dependencies across business flows and future initiatives. section 11.3.1
Regulated e-commerce modernization
A regulated North American e-commerce market leader used the heuristic to assess whether a candidate value stream was suitable as the first modernization slice. section 11.3.1
Use the figure to examine whether one horizontal support can serve multiple diverse verticals without creating problematic dependencies. section 11.3.1
