![]() ![]() Also, you can view a rollup of estimates, progress bars, and more on product backlogs. This type of grouping is recommended for organizations with several teams that want to view rollups associated with multiple teams and to take advantage of all portfolio planning tools.īy grouping work within a hierarchy, you can manage a portfolio of features that are supported by different development and management teams. You group requirements under Features, and Features under Epics, using parent-child hierarchical links. Work item tags are another way you can group requirements. Azure Boards supports this by providing portfolio work item types, portfolio backlogs and boards, and a Mapping tool to quickly link requirements to a portfolio work item. However, often you want to group requirements that support specific features or business objectives. The product backlog starts out as a flat list. Here the features backlog shows the sequence of features to ship.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |