Set team defaults

Last Update: 5/16/2017

Team Services | TFS 2017 | TFS 2015 | TFS 2013

Each team has access to a number of Agile tools. Each tool references the team's default area path(s). Several tools reference the team's default and active iteration paths or sprints. Most teams choose one area path and several iteration paths to support their work tracking activities. However, to support other scenarios, it's possible for teams to choose several area paths to appear on their backlogs and boards.

Prior to setting team defaults, add the teams you want and schedule your shared sprint schedule. Optionally, add area paths you want to use to group work items.

Several Agile tools reference the team's default area path, iteration path, and activated sprints to automatically filter the set of work items they display. Here's a quick summary of these tools:

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

You can view these queries by choosing the Create query link that appears on these tools' pages. (Note that you can't change the underlying query.) Lastly, you can set security permissions to control who has access to create, modify, or manage test plans and test suites under an area.

Team defaults referenced by backlogs and boards

Note: Some features are available only from Team Services or TFS 2017 or later versions. For details, see Set team defaults.

When you define a team, you define the team's:

  • 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. For example, one team might handle all work assigned to Customer Profile and Shopping Cart, while another team only manages work assigned to the Email area path. Also, the set of work items that appear on a backlog or board depend on the current State of a work item or it's parent-child status.

In addition, several tools reference the team's default iteration and selected iteration paths or sprints. For example, when you add new work items from a backlog or board view, or from a team dashboard, the system assigns the team's default area path and default iteration path to these work items.

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)
Kanban 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

Notes:

  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. Kanban boards, sprint backlogs, and task boards 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 Kanban board, sprint backlog, and task board. To learn more, see parent-child links between items.
  5. Work items whose State equals Removed don't appear on boards.

Backlog iteration versus default iteration

For TFS platforms, the default iteration is the same as the backlog iteration. The one value selected both filters items that appear on the team's backlogs and boards, and is assigned to work items created from the team context.

For Team Services, teams can now set a default iteration different from the backlog iteration. The backlog iteration determines which items appear on the team's backlogs and boards. And, the default iteration determines what value is assigned to work items created from the team context.

For both platforms, all work items that you create from your team context are automatically assigned both the team's default area path and default iteration path.

You navigate to your team context from the top navigation bar.

Choose another team from the team project menu

Open the admin context for your team

You set team defaults from the team admin context.

NOTE

For an overview of the administration context and the new navigation experience supported in Team Services, see Work in the web portal.

From a web browser, open the web portal administrative context for your team.

Open team admin context

If you're not a team administrator, get added as one. Only team or project administrators can change team settings.

Set team default area path(s)

All work items assigned to the area paths selected for a team appear on the backlogs and boards for that team.

  • From Team Services, you can select one or more area paths and optionally include their sub-area paths.
  • From TFS, you can select a single area path, and optionally include their sub-area paths.
    The default area path determines the default area path assigned to work items that are created from the team context.

Choose to include sub-area paths when you want to support rollup views of work performed across several teams or areas.

IMPORTANT

Work items that appear on more then one team's Kanban board can yield query results that don't meet your expectations. Because each team can customize the Kanban board columns and swimlanes, the values assigned to work items which appear on different boards may not be the same. The primary work around for this issue is to maintain single ownership of work items by team area path.

Team Services and TFS 2017 and later versions

  1. Open the Work, Areas admin page for the team context.

    Here, we navigate to the Fabrikam Fiber Team, the default team for the team project.

    Work, Area page for team, Team Services platform

  1. Choose the area path(s) to be active for each team. In general, feature teams set a single area path as their default.

    Work, Iterations page for team, Team Services platform

    In this instance, we choose to activate all three sub-area paths for the team project. This allows the management team to track progress across all three teams.

    Multiple area paths assigned to team, Team Services platform

  2. When you've finished, refresh the product backlog page for the team, and you'll see those work items assigned to the team. Add Area Path to the columns shown to see the assignments made to work items.

    Product backlog of team with multiple area paths assigned, Team Services platform

For TFS 2015 and earlier versions

  1. Open the Areas admin page for the team context.

    Here, we navigate to the Web team. The checked box indicates the area paths selected for the team. To exclude sub-areas, select the option from the area path context menu.

    Work, Area page forWeb  team, Team Services platform

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

    Backlog for Web  team

Select team sprints and default iteration path

You define sprints for the team project and then activate them for each team. You assign the default iteration to use when creating new work items.

You activate sprints for each team from the admin pages for each team context. The steps differ slightly depending on your platform.

For Team Services and TFS 2017 and later versions

  1. Open the Work, Iterations page for the team context.

    Here, we navigate to the Fabrikam Fiber Team.

    Work, Iterations page for team, Team Services platform

  2. Backlog iteration. Only work items assigned to an iteration equal to or under this backlog iteration appear in the team's backlogs and boards.

    Work, Iterations page for team, set team backlog iteration for backlogs and boards

    Also, all work items added through a team's backlog or board are assigned the backlog iteration.

  3. Default iteration. The default iteration defines the iteration used when a work item is created from the team dashboard (new work item widget) and queries page. You can use an explicit value or use @CurrentIteration to assign new work items to the team's current iteration. This is the same macro used in queries to list work items assigned to the currently active iteration assigned to the team.

    For example, you might want all new work items to be added to a future iteration path which you use to triage and assign to specific sprints at periodic intervals.

    Work, Iterations page for team, set team default for new work items

  4. Active sprints. Add an iteration for each sprint backlog you want active for the team. Add each sprint, one by one, by selecting it from the menu.

    Work, Iterations page for team, select sprint to activate, Team Services platform

    When you're done, you should see a list of sprints, similar to the following.

    Work, Iterations page for team, activates sprint list, Team Services platform

    If you don't see the sprints you need, or the dates aren't set, then return to the team project admin context and define them there.

  5. To see the newly activated sprint backlogs, refresh your team's product backlog page.

For TFS 2015 and earlier versions

  1. Open the Iterations page for the team context.

    Here we open the Iterations page for the Web team.

    Open team admin iterations page

    If your team isn't listed in the navigation row, open the Overview tab, select your team, and then return to the Iterations tab.

  2. Default iteration. Only work items assigned to an iteration equal to or under the default iteration appear in the team's backlogs and boards. Also, the default iteration defines the iteration used when a work item is created from the team dashboard (new work item widget) and queries page.

    Open the context menu for the iteration path you want.

    Here we set the P1 1 path. Only child iterations of the backlog iteration can be active for a team.

    Set team default iteration path

    This path determines which work items appear in your team backlogs and boards, and the default assigned to work items created from any area under your team's context.

  3. Active sprints. Check each box under the default iteration that you want active for the team.

    Here, the Fabrikam Fiber Web team activates Sprints 1 through 7.

    Select team active sprints

    Check boxes only appear for sprints defined under the default iteration path.

  4. To see the newly activated sprint backlogs, refresh your team's product backlog page.