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

Azure DevOps Services | Azure DevOps Server 2019 | TFS 2018 | TFS 2017 | TFS 2015 | TFS 2013

As your organization grows, you'll want to make sure that you configure your Agile tools to support that growth. To enable each feature team the autonomy it needs to manage their backlog and plan their sprints, they need their own set of team tools. For more information about features assigned to teams, see About teams and Agile tools.

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 team with visibility across each of these two teams.

Prerequisites

Add two feature teams

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 Code, new nav

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

    Create a sub-team 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 (aka 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 perform these additional tasks:

  1. From the web portal, choose the  gear settings icon to open the Project settings page for the project.

    Open project admin page

  2. 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 is 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.

    Create a sub-team with its own area path

  3. Select the team to configure it.

    Web portal, project admin context, Overview page, Select a team to configure it

    The Team Profile opens. From the team profile, you can Add team members and Add team administrators.

    Team profile, choose Iterations and areas link

  4. To select the set of sprints and area paths the team plans to use, see Define iteration paths (aka sprints) and configure team iterations.

    Important

    Team tools aren't available until the team's default area path is set.

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

  1. From the web portal, choose the  gear settings icon to open Project Settings.

    Open project admin page

  2. Create a 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 is 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.

    Create a sub-team with its own area path

  3. Select the team from the Overview tab to configure it.

    Web portal, admin context, project, Overview page, Select a sub-team to configure it

  4. To select the set of sprints the team plans to use, open the Iterations page for the team. See Define iteration paths (aka sprints) and configure team iterations.

  5. To change the area paths assigned to the team, open the Areas page. See Set team defaults, Set team default area path(s).

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 them 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 user to a project or to your organization or setup 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.

  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

    Web portal, Queries page, Bulk modify select work items

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

    Bulk save edited work items

    Web portal, Queries page, Bulk save selected work items

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 settings page for the default project team, and change the setting as shown.

    New nav, default project team configuration, Exclude work items defined in sub-area paths, new nav

  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

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

    Web portal, Admin context, default project, 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.

    Backlog view of default team

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

    Web portal, Admin context, default project, 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.

    Web portal, Backlog view of default team

Delete a team

  1. To delete a team, open Project Settings>Teams, choose the … context menu for the team you want to delete, and select the Delete option.

    Project Settings>Teams>Delete team

    Important

    Deleting a team deletes all team configuration settings, including team dashboards, backlogs, and boards. Data defined for work items assigned to the team are left unchanged. Once deleted, you can't recover the team configurations.

  2. To complete the delete operation, you must type the name of the WIT as shown.

    Delete team confirmation dialog

  1. To delete a team, open Project Settings>Work>Overview, choose the … context menu for the team you want to delete, and select the Delete option.

    Web portal, admin context-project level, Delete team

    Important

    Deleting a team deletes all team configuration settings, including team dashboards, backlogs, and boards. Data defined for work items assigned to the team are left unchanged. Once deleted, you can't recover the team configurations.

  2. To complete the delete operation, you must type the name of the WIT as shown.

    Delete team confirmation dialog

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.

Try this next

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.