Quick Notes83 words
Projects and teams in Azure DevOps — quick notes
Projects and teams — quick notes
| Guidance | Detail |
|---|---|
| Default | Fewer projects, more teams |
| Project = | A real security and process boundary |
| Team = | Lightweight slice: own backlog, iterations, dashboards |
| Team is defined by | The area paths it owns |
Choose multiple projects for: hard security isolation · separate process templates · genuinely disconnected work.
Trap: splitting into many projects for organisational tidiness, then paying cross-project friction forever.