VSTS | TFS 2018 | TFS 2017 | TFS 2015
While many teams can work with a flat list of items, sometimes it helps to group related items into a hierarchical structure. Perhaps you like to start with a big picture and break it down into smaller deliverables. Or, you've got an existing backlog and now need to organize it.
No matter your starting point, you can use portfolio backlogs to bring more order to your backlog. Use your backlogs to plan your project and to:
- Manage a portfolio of features that are supported by different development and management teams
- Group items into a release train
- Minimize size variability of your deliverables by breaking down a large feature into smaller backlog items
Use this topic to learn how to:
- View a backlog or portfolio backlog
- Add features and epics
- Add child items
With portfolio backlogs you can quickly add and group items into a hierarchy, drill up or down within the hierarchy, reorder and reparent items, and filter hierarchical views. Portfolio backlogs are one of three classes of backlogs available to you. For an overview of the features supported on each backlog and the two types of boards, see Backlogs, boards, and plans.
Feature availability: Epics are supported on VSTS and TFS 2015 and later versions. Each team can choose the backlog levels that are active as described in Select backlog navigation levels for your team.
View a backlog or portfolio backlog
To focus on one level of a backlog at a time, click the name of the backlog you want to view. If you don't see all three backlog levels— Epics, Features, and Backlog items— you can enable them for your team.
For example, when you click Epics, you'll see a list of all Epics in your team's active area paths. From there, you can drill down to see child features and backlog items.
Click Features to see a list of all features in your team's active area paths.
Add features and epics
Just as you can add items to your product backlog, you can add items to your features and epics backlogs. Here, we've added six features.
You can add epics in the same way. Simply open the Epics backlog.
Open each item (double-click, or press Enter to open the selected item) and add all the info you want to track. Enter as much detail as the team needs to understand the scope, estimate the work required, develop tests, and ensure that the end product meets acceptance criteria.
Reminder: The following screenshots illustrate the work item form for VSTS. Your forms may differ depending on what you have enabled, what process you chose when creating your team project—Agile, Scrum, or CMMI—and what platform you're working from, VSTS and TFS.
|Value Area||The area of customer value addressed by the epic, feature, or backlog item. Values include:
|Provide a relative estimate of the amount of work required to complete a Feature or Epic. Use any numeric unit of measurement your team prefers. Some options are story points, time, or other relative unit.|
Specify a priority that captures the relative value of an Epic, Feature, or backlog item compared to other items of the same type. The higher the number, the greater the business value.
Use this field when you want to capture a priority separate from the changeable backlog stack ranking.
|Time Criticality||A subjective unit of measure that captures the how the business value decreases over time. Higher values indicate that the Epic or Feature is inherently more time critical than those items with lower values.|
Specify the date by which the feature should be implemented.
Add child items
With your features defined, you're ready to add child items to them. From any backlog, you can add child items. You can add features to epics, and backlog items to features.
Here we add a product backlog item as a child to the Customer Web - Phase 1 feature.
Whenever you see the plus , you can add a child item. The work item always corresponds to the hierarchy of work item types that are defined for your team project.
For Scrum team projects, your hierarchy is as shown:
Because teams can also set bugs as tasks, bugs can be added as children of PBIs.
The work item types you'll see depends on the process you selected to create your team project.
If you want bugs to show up on your backlog and you're not seeing them, enable them for your team.
Try this next
Portfolio backlogs are not only a great way to organize your project plan, but also a great way to provide visibility of project plans across enterprise teams. With portfolio backlogs, management teams can gain insight into project status across all their development teams.