Edit

Share via

About teams and Agile tools

  • Article

Azure DevOps Services | Azure DevOps Server 2022 - Azure DevOps Server 2019

Learn how you can structure and use your teams and Agile tools to support your growing organization. When your team grows beyond its intended size—typically anywhere from 6 to 9 members—you might consider moving from a one team structure to a two-team structure. You can then set up a hierarchical team structure, which provides several advantages to managers for tracking progress across teams. For more information, see Add another team.

Depending on the size of your organization and your tracking needs, you can set up a team structure similar to the following image shown. Do so by defining teams and their associated area paths.

Each team has its own view of the work

The following scenarios apply:

  • Each feature team can be associated with a single feature area path—such as Customer Profile, Shopping Cart, Email—or several area paths.
  • Each management team, which focuses on a set of features, can choose several area paths to monitor.
  • Each feature team has its distinct backlog to plan, determine priority, and track work.
  • Portfolio or product owners can create their vision, roadmap, and goals for each release, monitor progress across their portfolio of projects, and manage risks and dependencies. For more information, see Portfolio management.

About area paths, feature teams, and management teams

Area paths serve the following purposes in Azure Boards:

  • Filter work items: Determine which work items appear on a team backlog or board.
  • Apply additional filtering: Further refine the work items that appear on a backlog or board. For details, see Interactively filter backlogs, boards, queries, and plans.
  • Group related work: Organize work that shares a relationship, such as belonging to the same product, feature, or other work-level grouping.
  • Restrict access: Set permissions to restrict modification of work items based on area path. Permissions can be configured for security groups.

Teams make their selections as follows:

  • Feature teams: Choose one or more area paths to specify which work items will appear on their backlogs and boards.
  • Management teams: Typically select all area paths that their feature teams work on. They might focus on Features and Epics, while feature teams concentrate on product backlog items such as User Stories (Agile), Product Backlog Items (Scrum), and Requirements (CMMI).

Note

Teams can be assigned a maximum of 300 Area Paths. For more information, see Work tracking, process, and project limits.

For more information, see Define area paths and assign to a team.

The default team

Each new project is configured with a default team named after the project. For example, the Fabrikam project is automatically configured with the Fabrikam team.

Backlogs, boards, and dashboards are set up for this default team, allowing you to start defining work items and your backlog immediately.

You can rename the default team and assign a different team as the default if needed.

Each team gets their own set of tools

Each team you create gains access to a suite of Agile tools and team assets. These tools enable teams to work autonomously while collaborating with other teams across the enterprise. Each team can configure and customize these tools to support their unique workflows and processes.

Screenshot showing Agile tools, team assets.

Note

In addition to team dashboards, you can add a project dashboard, which isn't specific to any one team. For more information, see Add, rename, and delete dashboards.

These tools automatically filter the set of work items they display by referencing the following items:

  • Default area path
  • Iteration path
  • Selected sprints

For more information about each tool and its configuration settings, see the following articles.

Area

Tool

Team configuration tasks

Backlogs

Sprints and Scrum

Boards

Widgets

Other tools

Not applicable

Many of these tools are built from system queries that reference the team's area path. For example, a team's default area path filters the work items that appear on the team's backlog. Work items created using an Agile tool automatically assign areas and iterations based on team defaults.

Team defaults referenced by backlogs and boards

Work items that appear on team backlogs and boards are determined by the team's Area Paths and Iteration Paths. When you add work items to a backlog or board, team defaults are used to assign field values.

When you define a team, you specify the following:

  • Selected Area Path(s)
  • Default Area Path
  • Selected Iteration Path(s)
  • Backlog Iteration Path
  • Default Iteration Path

All Agile tools reference the Area Path(s) defined for a team. The set of work items that appear on a backlog or board depends on the current State of a work item or its parent-child status.

Several tools also reference the team's default and selected Iteration Path or sprints. When you add a new work item from a team's backlog or board, the system assigns the team's Default Area Path and Default Iteration Path to it.

Note

New work items added through the Work Items page or the New Work Items widget on a team dashboard don't reference the Default Iteration Path assigned to the team. Instead, new work items are assigned the last Iteration Path selected by the user. New work items added through a team's Sprints backlog or taskboard are always assigned the Iteration Path associated with the selected sprint backlog or taskboard.

Agile tool

Area path (see note 1)

Iteration path

State

Portfolio or product backlogs

Selected area path(s)

Equal to or under team's backlog iteration path

Active (corresponds to a Proposed or InProgress state category, see notes 2, 3)

Boards (see note 4)

Selected area path(s)

Equal to or under team's backlog iteration path

Any state (see notes 3, 5)

Sprint backlogs (see note 4)

Selected area path(s)

Team's selected iteration paths

Any state (see notes 3, 5)

Task boards (see note 4)

Selected area path(s)

Team's selected iteration paths

Any state (see notes 3, 5)

New work item widget

Default area path

Default iteration path

n/a

Note

  1. Agile tools filter items based on the team's selected area path(s). Teams can choose whether to include or exclude items assigned to subarea paths.
  2. Work items whose State equals Closed, Done, or Removed (corresponding to a Completed category state) don't appear on portfolio and product backlogs.
  3. You can add custom workflow states and assign them to one of three state categories. The state categories"> determine which work items appear on backlog and board views.
  4. Boards, sprint backlogs, and taskboards only show the last node in a hierarchy, called the leaf node. For example, if you link items within a hierarchy that is four levels deep, only the items at the fourth level appear on the board, sprint backlog, and task board. For more information, see parent-child links between items.
  5. Work items whose State equals Removed don't appear on boards.

Structure hierarchical teams or scale agility within an enterprise

Although there's no concept of subteams, you can create teams whose area paths are under another team, which effectively creates a hierarchy of teams. For more information, see Add another team.

Also, the following articles walk you through the steps for configuring teams, area paths, and iterations to support portfolio management or enterprise organizations:

Team groups

When you add a team, a security group is automatically created with the team name. You can use this group to filter queries. The name of team groups follows the pattern [Project Name]\Team Name. For example, the following query finds work assigned to members of the [Fabrikam Fiber]\Email team group.

Web portal, Queries page, Query that uses In Group operator and team group name

You can also use the @mention control within discussions and pull requests to notify all members of a team. Start entering the name of a team or a security group, select the search icon, and then select from the options listed. For more information, see Use @mentions to further discussion.

Work on more than one team

Can a user account belong to more than one team?

Yes. You can add user accounts as members of the project or to one or more teams added to the project. If you work on two or more Scrum teams, make sure you specify your sprint capacity for each team you work on.

Team member permissions

By default, team members inherit the permissions afforded to members of the project Contributors group. Members of this group can add and modify source code, create and delete test runs, and create and modify work items. Team members can collaborate on a Git project or check in work to the team's code base.

Default permissions assigned to team contributors

For more information about limiting access, see Set permissions and access for work tracking.

Summary

Note: The author created this article with assistance from AI. Learn more