Add a team, move from one default team to several teams

Azure DevOps Services | Azure DevOps Server 2020 | Azure DevOps Server 2019 | TFS 2018 - TFS 2013

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.

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.

For a good understanding on how to remain Agile as you add teams, review the Scale Agile to Large Teams article.

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.

Prerequisites

  • If you don't have a project yet, create one.
  • If you're not a Project Administrator, get added as one. Only members of the Project Administrators group can add and delete teams.

Add two feature teams

Note

To enable the user interface for the New Teams Page, see Manage or enable features.

Add and configure two teams, Email and Voice. Here we show you how to add and configure the Email team.

  1. From the web portal, choose Project settings and open Teams. Open Project settings, and then Teams

  2. Choose New team. Give the team a name, and optionally a description.

    Create a subteam with its own area path

  3. Select the team to configure it. To select the set of sprints and area paths the team plans to use, choose Iterations and areas See Define area paths and assign to a team and Define iteration paths (also known as sprints) and configure team iterations.

    Team profile, choose Iterations and areas link

    Important

    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:

To configure other team features, see Manage teams and configure team tools.

The New Teams user interface isn't supported for Azure DevOps Server 2020 and earlier versions.

Add team members

If you're moving from one team to two teams, team members already have access to the project. If you're setting up a team structure for the first time, adding user accounts as team members provides access to the project and team assets. Access to the project is required to support sharing code and planning and tracking work.

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.

Note

You must first add a user to a project or to your organization or set up your account to work with Azure AD. This way you can add user identities to a team.

Note

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.

For details, see Add users to a project or specific team.

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.

Browser

  1. The quickest way to do this, is to create a query of all work items you want to reassign, multi-select those items belonging to each team, and bulk edit the area path.

    Web portal, Queries page, Bulk modify select work items

  2. After you bulk modify, do a bulk save.

    Bulk save edited work items

  1. The quickest way to do this, is to create a query of all work items you want to reassign, multi-select those items belonging to each team, and bulk edit the area path.

    Web portal, Queries page, Bulk save selected work items

  2. After you bulk modify, do a bulk save.

    Web portal, Queries page, Bulk save selected work items

Azure DevOps CLI

You can move work items to a new area paths using az boards work-item update.

az boards work-item update --id
                           [--area]
                           [--assigned-to]
                           [--description]
                           [--discussion]
                           [--fields]
                           [--iteration]
                           [--open]
                           [--reason]
                           [--state]
                           [--title]

Parameters

  • id: Required. The ID of the work item to update.
  • 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.

Note

For Azure DevOps Server 2020, you can use the following command to set the default server instance, collection, and project.
az devops configure --defaults organization=https://ServerName/CollectionName project=ContosoWebApp

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.

C:\WINDOWS\system32>az boards work-item update --id 487 --area "Fabrikam Fiber\Service Delivery\Email"
{
  "fields": {
    "Microsoft.VSTS.Common.BacklogPriority": 1944453550.0,
    "Microsoft.VSTS.Common.Priority": 1,
    "Microsoft.VSTS.Common.Severity": "3 - Medium",
    "Microsoft.VSTS.Common.StateChangeDate": "2016-11-15T23:24:26.143Z",
    "Microsoft.VSTS.Common.ValueArea": "Business",
    "System.AreaPath": "Fabrikam Fiber\\Service Delivery\\Email",
    "System.AssignedTo": {
      "_links": {
        "avatar": {
          "href": "https://dev.azure.com/kelliott/_apis/GraphProfile/MemberAvatars/msa.ZmUwYjk5NmYtZTAyNS03NzBkLTgxNmYtMzk1NDQwYzViMzgw"
        }
      },
      "descriptor": "msa.ZmUwYjk5NmYtZTAyNS03NzBkLTgxNmYtMzk1NDQwYzViMzgw",
      "displayName": "Raisa Pokrovskaya",
      "id": "bd30c189-db0f-4dd6-9418-5d8b41dc1754",
      "imageUrl": "https://dev.azure.com/kelliott/_apis/GraphProfile/MemberAvatars/msa.ZmUwYjk5NmYtZTAyNS03NzBkLTgxNmYtMzk1NDQwYzViMzgw",
      "uniqueName": "fabrikamfiber5@hotmail.com",
      "url": "https://spsprodeus21.vssps.visualstudio.com/A380ed149-33d0-4d78-a7ed-89921802f389/_apis/Identities/bd30c189-db0f-4dd6-9418-5d8b41dc1754"
    },
    "System.BoardColumn": "New",
    "System.BoardColumnDone": false,
    "System.ChangedBy": {
      "_links": {
        "avatar": {
          "href": "https://dev.azure.com/kelliott/_apis/GraphProfile/MemberAvatars/msa.MmZhZDE3ZDAtMjRmZi03YjY5LWE5ZTUtMzYxMzQwOTZlNzNk"
        }
      },
      "descriptor": "msa.MmZhZDE3ZDAtMjRmZi03YjY5LWE5ZTUtMzYxMzQwOTZlNzNk",
      "displayName": "Kathryn",
      "id": "a0f9fe47-8a0a-438c-adfb-403c69664618",
      "imageUrl": "https://dev.azure.com/kelliott/_apis/GraphProfile/MemberAvatars/msa.MmZhZDE3ZDAtMjRmZi03YjY5LWE5ZTUtMzYxMzQwOTZlNzNk",
      "uniqueName": "kebelliott@msn.com",
      "url": "https://spsprodeus21.vssps.visualstudio.com/A380ed149-33d0-4d78-a7ed-89921802f389/_apis/Identities/a0f9fe47-8a0a-438c-adfb-403c69664618"
    },
    "System.ChangedDate": "2019-08-15T20:36:18.34Z",
    "System.CommentCount": 0,
    "System.CreatedBy": {
      "_links": {
        "avatar": {
          "href": "https://dev.azure.com/kelliott/_apis/GraphProfile/MemberAvatars/msa.MmZhZDE3ZDAtMjRmZi03YjY5LWE5ZTUtMzYxMzQwOTZlNzNk"
        }
      },
      "descriptor": "msa.MmZhZDE3ZDAtMjRmZi03YjY5LWE5ZTUtMzYxMzQwOTZlNzNk",
      "displayName": "Kathryn",
      "id": "a0f9fe47-8a0a-438c-adfb-403c69664618",
      "imageUrl": "https://dev.azure.com/kelliott/_apis/GraphProfile/MemberAvatars/msa.MmZhZDE3ZDAtMjRmZi03YjY5LWE5ZTUtMzYxMzQwOTZlNzNk",
      "uniqueName": "kebelliott@msn.com",
      "url": "https://spsprodeus21.vssps.visualstudio.com/A380ed149-33d0-4d78-a7ed-89921802f389/_apis/Identities/a0f9fe47-8a0a-438c-adfb-403c69664618"
    },
    "System.CreatedDate": "2016-11-15T23:24:26.143Z",
    "System.IterationPath": "Fabrikam Fiber\\Release 1\\Sprint 4",
    "System.Reason": "New defect reported",
    "System.State": "New",
    "System.TeamProject": "Fabrikam Fiber",
    "System.Title": "Check issues with permissions",
    "System.WorkItemType": "Bug",
    "WEF_1C5A9C9263944104B13DEF47AB16892F_Kanban.Column": "Backlog",
    "WEF_1C5A9C9263944104B13DEF47AB16892F_Kanban.Column.Done": false,
    "WEF_728F47E9D8BF470AB800917CB3E81BD0_Kanban.Column": "New",
    "WEF_728F47E9D8BF470AB800917CB3E81BD0_Kanban.Column.Done": false,
    "WEF_7ADD68E5D87D4B75AA575F3757C5FB14_Kanban.Column": "New",
    "WEF_7ADD68E5D87D4B75AA575F3757C5FB14_Kanban.Column.Done": false,
    "WEF_7E5E0F9353CB4F0091FCCE45C49F5636_Kanban.Column": "New",
    "WEF_7E5E0F9353CB4F0091FCCE45C49F5636_Kanban.Column.Done": false,
    "WEF_E825423B472B438797D4385614A48F91_Kanban.Column": "New",
    "WEF_E825423B472B438797D4385614A48F91_Kanban.Column.Done": false
  },
  "id": 487,
  "relations": [
    {
      "attributes": {
        "isLocked": false,
        "name": "Parent"
      },
      "rel": "System.LinkTypes.Hierarchy-Reverse",
      "url": "https://dev.azure.com/kelliott/56af920d-393b-4236-9a07-24439ccaa85c/_apis/wit/workItems/546"
    },
    {
      "attributes": {
        "isLocked": false,
        "name": "Child"
      },
      "rel": "System.LinkTypes.Hierarchy-Forward",
      "url": "https://dev.azure.com/kelliott/56af920d-393b-4236-9a07-24439ccaa85c/_apis/wit/workItems/374"
    }
  ],
  "rev": 24,
  "url": "https://dev.azure.com/kelliott/56af920d-393b-4236-9a07-24439ccaa85c/_apis/wit/workItems/487"
}

Azure DevOps CLI commands aren't supported for Azure DevOps Server 2019 and earlier versions.


Configure the default project team

One last step in moving from one team to two teams requires configuring the default project team to exclude sub-areas.

  1. Open Project settings > Team configuration > Areas settings page for the default project team, and change the setting as shown.

    Default project team configuration, Exclude work items defined in sub-area paths

  2. Refresh the product backlog page for the team, and you'll see only those work items assigned to the Fabrikam Fiber area path.

Product backlog, default project team

The New Teams user interface isn't supported for Azure DevOps Server 2020 and earlier versions.

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

For more information on setting the above permissions or restricting access for select users, see Set permissions and access for work tracking.

If your Azure DevOps Server or TFS deployment is integrated with SQL Server Reports, you'll need to Grant permissions to view or create SQL Server reports to team members.

If your TFS deployment is integrated with a SharePoint product or SQL Server Reports, you'll need to manage membership for those products separately from their websites.

Next steps

Once you've created a team, you'll want to 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.