Team Services | TFS 2017 | TFS 2015 | TFS 2013
Agile tools provide each team a wealth of ways to gain visibility into their work—to manage priorities and status and to monitor progress and trends. However, how do you gain visibility across several teams? What tools should you use?
You have three main ways to track progress across several teams.
- Management teams can define Delivery Plans that provide visibility into the deliverables several teams have scheduled
- Each management team can use their Agile tools, and in particular portfolio backlogs, to gain visibility of the feature teams defined under their area path
- Management teams can create dashboards that monitor status, progress, and trends across several teams.
For an overview of all team tools, see Configure team settings.
Delivery Plans support a view of team backlogs on a calendar timeline
With a Delivery Plan, you gain a tailor-made view across several teams and their development backlogs—stories, features, or epics. You can use these views to drive alignment across teams by overlaying several backlogs onto your delivery schedule.
Feature availability: Delivery Plans, a Visual Studio Marketplace extension, is available for Team Services and TFS 2017.2 and later versions. All users with basic access can view, add, and configure Delivery Plans. Stakeholders, however, don’t have access to Delivery Plans.
When you configure a Delivery Plan, you select the teams and backlog levels of interest. You can then interact with the plan to update it and drill into more details. To learn more about Delivery Plans, see Review team plans.
Use portfolio backlogs to track features and epics
The first level of gaining visibility across several teams is to configure your teams and backlogs to support the views you want.
We recommend that you structure your teams as follows:
- Add a management team for a group of feature teams; these teams own epics and turn on only the Epic portfolio backlog level
- Add feature teams to manage features, stories and tasks, and turn on the stories and features backlog levels
The management team creates the epics, and then they or their feature teams break the epics down into features and then map their features to the epics on the management backlog.
By breaking down large goals, epics, scenarios, or features into smaller ones, teams can make better estimates and identify risks and dependencies.
Limiting the backlog levels for each teamEpics for management teams and Features and Stories for feature teamshelps each team to stay focused on monitoring the progress of their work. For details on managing team backlog levels, see Select backlog navigation levels.
With the multi-team portfolio backlog view, you can:
- Review priorities with your team and reorder features to support current priorities
- You can drill down to see the status of each feature's child user stories or PBIs
- Filter the backlog based on keyword or tag to focus on specific teams or categorized items
- (Optional) You can use the mapping feature to map user stories or PBIs to features
Management teams can drill down from their portfolio backlog to see how epics are progressing.
And, feature teams can turn on Show parents on their backlogs to see context and even those stories
When estimating stories or product backlog items, start with one story point per person per day. Feature teams can later calibrate and adjust those estimates as needed. For example, the velocity of a seasoned team will be higher than a new team. The size of the work stays the same, but a seasoned team can just deliver faster.
Add management dashboards with multi-team views
A second method for gaining visibility across teams is to define multi-team focused dashboards that let you view progress, status, and trends. You do this primarily by defining queries that either capture the progress of a single team or several teams. You can then create charts and view trends for each team or for several teams.
The two areas of most interest to management teams is project health and bug debt. The widget catalog provides 10+ widgets you can add to a dashboard to track the status, progress, and health of your project and teams. Also, you can find additional widgets in the Visual Studio Marketplace.
For example, here we've added three query-based charts, one for each team, to a dashboard that shows the active and resolved bugs over the previous 4 weeks.
When defining multi-team dashboards, consider the following:
- What are you wanting to learn and how will it drive your organization's actions
- What time frame is of interest.
Project health and progress against goals dashboard
Use the Query Results widget to provide a list of features by state:
- Completed features (Done or Closed)
- New features (New or Proposed)
- Features being actively worked (In Progress or Active)
Technical debt, bug debt and activity dashboard
Another measure of project health and the health of the teams is to monitor bug activity and bug debt. Consider the charts you can create that will help you answer these questions:
- Are bugs getting fixed? at a rate that's acceptable?
- How stale are bugs?
- Is the bug debt per team being maintained?
- Is the ratio of high priority bugs being kept within organizational goals?
For tips on creating queries based on counts or numeric fields, see Query by numeric field.
As you can see, there are a number of ways you can monitor progress and trends across several teams. The methods you choose will depend on your focus and organizational goals.
Here are some additional topics that address working with multiple teams:
- Backlogs, boards, and plans
- Review team plans
- Multiple teams
- Portfolio management
- Configure team settings
- Practices that scale
Limitations of multi-team Kanban board views
While the management teams you configure can use the Kanban board to monitor feature progress by turning on the Features backlog, there are limitations inherent within these views. Even if the management team and the feature teams configure their Feature Kanban board columns with identical workflow mapping, updating the Features on one team's Kanban board won't be reflected on another team's Kanban board. Only when the work item state changes does the card column reflect the same on all boards.
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. Another option is to add custom workflow states which all teams can use. FOr details, see Customize your work tracking experience.