Quick Notes145 words
Projects and teams in Azure DevOps — quick notes
Projects and teams — quick notes
| Guidance | Detail |
|---|---|
| Default | Start with one project for lower administration and optimized cross-links |
| Project scope | Data, access, administration, and process assignment—not automatic hard isolation |
| Process | Selected per project; several projects may share one inherited process |
| Team | Own backlogs, boards, dashboards, and configurable assets |
| Backlog contents | Selected area and iteration paths; backlog levels, state, hierarchy, and bug behavior also matter |
| Multiple projects | Select-group access · business-unit process · separate administration · customization testing · OSS |
| Cross-project work | Less optimized links · explicit resource references and authorization · project-scoped administration |
Trap: treating either “one project” or “hard project isolation” as a universal rule.
Primary sources
- https://learn.microsoft.com/en-us/credentials/certifications/resources/study-guides/az-400
- https://learn.microsoft.com/en-us/azure/devops/organizations/projects/about-projects?view=azure-devops
- https://learn.microsoft.com/en-us/azure/devops/organizations/settings/about-teams-and-settings?view=azure-devops
- https://learn.microsoft.com/en-us/azure/devops/organizations/settings/work/manage-process?view=azure-devops
- https://learn.microsoft.com/en-us/azure/devops/pipelines/process/resources?view=azure-devops