Team Services | TFS 2017 | TFS 2015 | TFS 2013
Portfolio backlogs provide product owners insight into the work performed by several agile feature teams. Product owners can define the high-level goals as Epics or Features, and feature teams can break these down into the user stories they'll prioritize and develop.
By setting up a team structure like the one shown, you provide each feature team with their distinct backlog to plan, prioritize, and track their work. And, 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.
Set up a hierarchical team and backlog structure when you want to support:
- Autonomous feature teams that can organize and manage their backlog of work
- Portfolio management views for planning epics and features and monitoring progress of subordinate feature teams
- Assign backlog items to feature teams from a common backlog
The images you see from your web portal may differ from the images you see in this topic. These differences result from updates made to Team Services or your on-premises TFS, options that you or your admin have enabled, and which process was chosen when creating your team project—Agile, Scrum, or CMMI. However, the basic functionality available to you remains the same unless explicitly mentioned.
Work items are denoted with icons for Team Services and TFS 2017.2 and later versions. For an overview of changes in the navigation experience and working within the user and administration contexts, see Work in the web portal.
Management view of team progress
The Fabrikam Account Management portfolio owner has several campaigns to initiate and deliver in the coming year. He creates an epic for each campaign and then breaks each epic down into various features that contribute to each campaign.
With the hierarchical structure implemented, portfolio owners working in Account Management can view the epic, feature, and product backlogs for their area.
All work items under the Fabrikam/Account Management area path appear in their backlog view. You can expand a single item or use the expand and collapse icons to expand or collapse one level of the hierarchy.
Feature team backlog ownership and view of progress
The Customer Profile feature team's view of the backlog only includes those work items assigned to their area path, Fabrikam/Account Management/Customer Profile. Here we show parents which provides a few of the features and epics to which the backlog items belong. Items that are owned by other teams appear with hollow-filled bars. For example, Mobile feedback and Text alerts belong to the Account Management team.
Add Node Name to the column options to show the team assigned to the work item.
Each feature team has its own team home page, backlog, Kanban board, and task board. These pages only show work relevant to each team, based on assignments made to the work item area and iteration paths.
Assign work from a common backlog
While the hierarchical team and backlog structure works well to support autonomous teams to take ownership of their backlog, it also supports assigning work to teams from a common backlog. During a sprint or product planning meeting, product owners and development leads can review the backlog and assign select items to various teams.
In this Account Management view, all Product Backlog Items still under Account Management have yet to be assigned.
During the planning meeting, you can open each item, make notes, and assign the item to the team to work on it.
Here, all backlog items have been assigned to feature teams. While all features and epics remain owned by Account Management.
You can multi-select work items and perform a bulk edit of the area path. In Visual Studio Team Services you can do this from any backlog. From on-premises TFS, you can create a backlog query and perform bulk updates from the query results.
Set up hierarchical teams and backlogs
The first step is to add a team for each feature team and management area. When you finish, you'll have a set of teams similar to the ones shown.
You'll need to be a project administrator to perform these steps.
To add a team, give the team a name, and make sure to select Create an area path with the name of the team.
To access this page, choose the gear icon from your team home page.
Repeat this step for all teams and management areas.
In this next step, you want to move the areas paths associated with feature teams from a flat structure to a hierarchical structure. For details on this step, see Set team default area paths
Flat area structure Hierarchical area structure
You do this by opening each area path associated with a feature team and change its location to be under the management area path. For example, here we move the Customer Profile area path to under Account Management
Repeat this step for all feature team area paths.
Next, you want to change the area path setting for management areas to include sub-area paths. The default setting for all teams is to exclude sub- area paths.
Here we choose to include sub-area paths for the Account Management area.
Repeat this step for all your management areas. Also, if you want to enable rollup across all feature teams and management areas to the top level area, repeat this step for the default team. In our example, that corresponds to Fabrikam.
Add team administrators for each feature team and management area. You do this from the Overview page of the team admin context.
Add the account identity, for example the product owner, development lead, or other team member who has primary responsibility for planning and reporting progress.
In this way, the team administrators can add additional team admins and team members. They can also configure their team settings and manage their Agile tools and team assets.
Optionally, grant team administrators additional permissions.
Define a single sprint cadence for all teams
If your feature teams use Scrum and work in sprints, you'll want to set up a series of sprints that all teams can use. By default, you'll see a set of predefined sprints. Add more sprints and set their sprint dates as described in Add iterations and set iteration dates.
You do this from the team project admin context.
Here we've defined the start and end dates of the first 6 sprints corresponding to a 3-week cadence.
Customize Agile tools and configure team settings
These next set of steps can be performed by a team administrator.
- Add team members
- Select sprints for the team
- Activate backlog levels
- Show bugs on backlogs and boards
See Configure team settings for an overview of all Agile tools and team assets.
Try this next
With the hierarchical set of teams in place, you're well positioned to start planning and using the Agile tools available. To take the next steps in planning your portfolio of projects, see these articles:
- Review team plans
- Add management dashboards with multi-team views.
- Work with multi-team ownership of backlog items
- Select backlog navigation levels for your team
- Track capacity when working on more than one team
- Create your backlog
- Organize your backlog
- Customize your work tracking experience
If you need additional portfolio backlogs—for example, Scenarios or Initiatives—you can add them as well.
Track dependencies across teams
The simplest way to track dependencies is to link work items using the Related link type. You can then create queries that find work items containing these relationships.
Additionally, you can use the Predecessor and Successor links when time dependencies factor in.
See Manage dependencies, link work items to support traceability to learn more.