AZ-400 Question 238
Single answerYou are tasked with setting up a new Azure DevOps environment for a large software development initiative. The project has multiple feature teams, each requiring its own backlog, dashboards, and iteration schedules. Leadership wants to maintain a consolidated view to track cross-team progress. You want to minimize administration overhead while supporting each team� customization needs. Which approach should you recommend?
- A
Create a single Azure DevOps project and define each feature team as a separate team with dedicated area paths and iteration paths.
- B
Create a separate Azure DevOps project for each feature team.
- C
Use multiple Azure DevOps organizations, each with a single project for one feature team.
- D
Define one centralized Azure DevOps team across all features, and use custom queries to separate tasks.
Show answer and explanation
Correct answer: A
Explanation
Azure DevOps best practices recommend using a single project for cohesive management and reporting while leveraging multiple teams with dedicated area and iteration paths. This approach allows each feature team to have customized backlogs, dashboards, and iterations, while still allowing leadership to see a unified, cross-team view. For more information, refer to Microsoft� documentation on team and backlog management in Azure DevOps (https://docs.microsoft.com/azure/devops/organizations/settings/work/manage-teams).
- A. Correct.
Option 1 is correct. By creating a single project and defining multiple teams, each with its own area and iteration paths, teams can have isolated backlogs, boards, and dashboards. Leadership can still track cross-team progress in one place, minimizing overhead and making centralized governance easier.
- B. Incorrect.
Option 2 is incorrect. While creating separate projects can isolate each team, it complicates cross-team visibility and increases administrative complexity, as you have to manage multiple projects, their security, and shared resources separately.
- C. Incorrect.
Option 3 is incorrect. Using multiple organizations is an even more significant split than multiple projects, leading to overhead in licensing, administration, and consolidated reporting. It� typically not recommended unless you have distinct business units or security requirements that cannot be met within a single organization.
- D. Incorrect.
Option 4 is incorrect. Maintaining a single team and then relying on custom queries for each feature team does not give teams their own backlogs or boards. It becomes cumbersome to manage different iterations and area paths for multiple teams under a single team structure.