Define features and epics
Azure Boards | Azure DevOps Server 2019 | 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:
- Determine what is a good feature or epic
- View a backlog or portfolio backlog
- Add features and epics
- Add child items
To understand the features supported on each backlog and board, and how each display hierarchical items, see Backlogs, boards, and plans. To learn how to track progress across teams, see Visibility across teams.
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.
- You must be a member of the Contributors group or be granted Stakeholder access to add, modify, or remove work items
- And, you must have your View work items in this node, and your Edit work items in this node permissions set to Allow for the area path assigned to the work item.
To learn more, see Set permissions and access for work tracking.
What comprises a feature or epic?
The epics and features that you create should reflect your business focus. As user stories or product backlog items roll up into features, and features roll up into epics—you'll want to name your features and epics with that in mind.
A feature typically represents a shippable component of software. An epic represents a business initiative to be accomplished. Here are a few examples of each.
- Add view options to the new work hub
- Add mobile shopping cart
- Support text alerts
- Refresh the web portal with new look and feel
- Increase customer engagement
- Improve and simplify the user experience
- Implement new architecture to improve performance
- Engineer the application to support future growth
- Support integration with external services
- Support mobile apps
View a backlog or portfolio backlog
To focus on one level of a backlog at a time, choose 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 choose 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.
Your web portal uses either the New navigation or Previous navigation user interface. Choose the New navigation tab if the New Navigation feature is enabled. You'll see a vertical sidebar along with other navigational features when New Navigation has been enabled for the signed-in user or the organization. Choose Previous navigation when you see a top-level, blue-bar—indicating that New navigation isn't enabled. For more information, see Web portal navigation.
Choose the New navigation tab for guidance. Azure DevOps Server 2019 supports the New Navigation user interface. For more information, see Web portal navigation.
Choose the Previous navigation tab for guidance. TFS 2018 and earlier versions only support the previous navigation user interface. For more information, see Web portal navigation.
Each team can choose the backlog levels that are active as described in Select backlog navigation levels for your team.
Add features and epics
Just as you can add items to your product backlog, you can add items to your features and epics backlogs.
Add details to a feature or epic
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.
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 your web app, options that you or your admin have enabled, and which process was chosen when creating your project—Agile, Scrum, or CMMI.
|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 able 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.
You can also add child user stories (Agile), or product backlog items (Scrum) or requirements (CMMI) from the Kanban board for Features. And, you can add child features from the Epic board. For details, see Kanban board features and epics. Also, you can quickly parent or reparent children from a backlog using the mapping pane as described in Organize your backlog, map child work items to parents.
For Scrum 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 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.