Designing Azure DevOps Projects for Real-World Complexity
· 8 min read
Companion blog for deciders: Die Architektur der Empirie: Wie die Azure DevOps Struktur Management und Entwicklung vereinen kann
The most consequential Azure DevOps configuration decision you make is also the easiest to get wrong: how to structure your project. Microsoft's default guidance is clear — start with one project and scale using Teams, Area Paths, and Iteration Paths. This guide walks through three scenarios of increasing complexity, including a concrete, tested solution for the hardest case: multiple teams sharing work across multiple products. It also covers the narrow set of situations where a second project genuinely makes sense.