Azure DevOps Services | Azure DevOps Server 2020 | Azure DevOps Server 2019 | TFS 2018
As your organization grows, make sure that you configure your Agile tools to support that growth. Each team needs their own set of team tools to enable the autonomy it needs to manage their backlog and plan their sprints. For more information about features assigned to teams, see About teams and Agile tools.
Each new project is configured with a default team with the project name. You can rename the default team and you can reassign a new team as the default. For a good understanding on how to remain Agile as you add teams, review the Scale Agile to Large Teams article.
Use this article to learn how to perform the following tasks:
Move from one team to two teams
Add members to a team
Move work items to a team backlog
Set the default team for a project
Note
This article describes how to add a team or team members to a project defined in Azure DevOps. To learn about Microsoft Teams, see the Marketplace extension, Microsoft Teams Integration.
As your team grows, you can easily move from one team to two. In this example, we add two feature teams, Email and Voice, and maintain the Fabrikam Fiber default team with visibility across each of these two teams.
To add a team, you must be a member of the Project Administrators group. See Change project-level permissions. Only members of the Project Administrators group can add and delete teams.
Team tools aren't available until the team's default area path is set. If you haven't created one or more Area Paths for the team to use, then do that now. Area Paths must be created for the project first, then assigned to the team.
From the team profile, you can do these additional tasks:
Team tools aren't available until the team's default area path is set. If you haven't created one or more Area Paths for the team to use, then do that now. Area Paths must be created for the project first, then assigned to the team.
From the team profile, you can do these additional tasks:
Choose New team. Give the team a name, and make sure to select Create an area path with the name of the team. Or, leave it unchecked and assign the default area path for the team after it's created. You can choose an existing area path or add a new one at that time. Team tools aren't available until the team's default area path is set.
If you don't specify a top number, 100 teams are returned. To list all teams in a project, specify a number for top which is greater than the current number of teams defined.
Parameters
project: Optional. Name or ID of the project. Example: --project "Fabrikam Fiber". You can configure the default project using az devops configure -d project=NAME_OR_ID. Required if not configured as default or picked up via git config.
skip: Optional. Number of teams to skip.
top: Optional. Maximum number of teams to return.
Example
For example, the following command returns the 11 teams defined in the Fabrikam Fiber project. For addition output formats, see Output formats for Azure CLI commands.
Each team is assigned a unique ID.
az devops team list --project "Fabrikam Fiber" --output table
ID Name Description
------------------------------------ ------------------ ----------------------------------------------------------------------------
7f099146-29a2-4798-9949-77c9f5f79653 Account Management Management team focused on creating and maintaining customer services
2017b37a-486b-4222-ac84-b8b9eefa540e Customer Profile Feature team focused on securing account data
a90cd8f0-8e0d-42d6-aeb2-13442b826730 Email Feature team delivering email apps
a48cb46f-7366-4f4b-baf5-b3632398ed1e Fabrikam Team The default project team. Was Fabrikam Fiber Team
e42fccbc-d96f-4c98-8168-7a85ecede548 Internet Feature team developing web apps
b70aa504-33b4-4d17-a85d-0fbf4829a154 Phone Feature team delivering phone apps
43e6bd2e-696f-492c-bbf7-9cde9cd420ea Service Delivery Management team responsible for ensure high performance delivery of services
8920d2ec-eed1-4792-8934-82a57abce7c2 Service Status Feature team focused on monitoring and addressing service issues
9c676c8c-1910-4f73-b7b9-a946b5c551ae Shopping Cart Feature team managing shopping cart apps
64b86488-e105-4901-ba43-ffd48137bb93 TV Feature team developing TV apps
cda2b9b0-0335-4a0d-8bd0-67611d64ce9d Voice Feature team focused on voice communications
Azure DevOps CLI commands aren't supported for Azure DevOps Server on-premises.
Add team members
When you set up a team structure for the first time, add user accounts as team members. This action provides access to the project and team assets. Moving from one team to two teams, team members already have access to the project. To support sharing code, planning, and tracking work, you must have access to the project.
Several Agile tools, like capacity planning and team alerts, and dashboard widgets are team-scoped. That is, they automatically reference the user accounts of team members to support planning activities or sending alerts.
The first time you add a user account, you must enter the full domain name and the alias. Afterwards, you can browse for that name by display name as well as account name. To learn more, see Set up groups for use in Azure DevOps Server deployments.
Move work items under teams
Now that your two feature teams are configured, you need to move existing work items from their current assignments to the team's default area path. This way, the work items show up on each team's backlog.
area: Optional. Absolute path of an area. Example: --path \ProjectName\Area\AreaName.
assigned-to: Optional. Name of the person the work item is assigned to Jamal.
description: Optional. Description of the work item.
discussion: Optional. Comment to add to a discussion in a work item.
fields: Optional. Space separated "field=value" pairs for custom fields you want to set.
iteration: Optional. Absolute path of an iteration. Example: \ProjectName\Iteration\IterationName.
open: Optional. Open the work item in the default web browser.
reason: Optional. Reason for the state of the work item.
state: Optional. State of the work item, for example, Active.
title: Optional. Title of the work item.
Example
You can only move one work item at a time using Azure DevOps CLI. In this example, we move work item ID=487 under the Fabrikam Fiber/Service Delivery/Email area path.
az boards area team add --path --team
[--include-sub-areas {false, true}]
[--project]
[--set-as-default]
Parameters
path: Required. Absolute path of an area. Example: --path \ProjectName\Area\AreaName.
team: Required. Name or ID of the team.
include-sub-areas: Optional. Include child nodes of the area path. Accepted values: false, true.
project: Optional. Name or ID of the project. Example: --project "Fabrikam Fiber".
set-as-default: Optional. Specify as the default area path for the team. Default: False.
Example
For example, the following command adds the Voice area path to the Voice team for the Fabrikam Fiber project, sets it as the default and to include sub-areas.
az boards area team add --path "\Fabrikam Fiber\Voice" --team Voice --project "Fabrikam Fiber" --include-sub-areas --set-as-default --include-sub-areas true --output table
Area Include sub areas Is Default
------------------------------------- ------------------- ------------
Fabrikam Fiber\Service Delivery\Voice False False
Fabrikam Fiber\Voice True True
Azure DevOps CLI commands aren't supported for Azure DevOps Server on-premises.
Grant team members additional permissions
For teams to work autonomously, you may want to provide them with permissions that they don't have by default. Suggested tasks include providing team administrators or team leads permissions to:
Create and edit child nodes under their default area path
Create and edit child nodes under an existing iteration node
Create shared queries and folders under the Shared Queries folder
Configure your Agile tools to support how your team works. Also, consider adding one or more users as team administrators. Team administrators have the necessary permissions to add team members, add a picture to the team profile, and configure and manage all team features.
.
for that team and select Set team as project default.
