Using portfolio backlogs, you can drill down from one backlog to another to view the level of detail you want. You can do this by defining features and mapping PBIs to features. When you manage a suite of products or user experiences, you might want to view the scope and progress of work across the product portfolio. For other customization options, see Customize your work tracking experience. You can customize the Kanban board to support more swim lanes or columns. Dragging items to a new state column updates both the State and Reason fields.
Teams can use the Kanban board to update the status of PBIs, and the sprint taskboard to update the status of tasks. The item is moved to the Done state when the team has completed all its associated tasks and the product owner agrees that it has been implemented according to the Acceptance Criteria.The team updates the status to Committed when they decide to commit to working on it during the sprint.Most of the time, items near the top of the Product Backlog are in the Approved state, while items toward the middle and bottom are in a New state The product owner moves the item to Approved after it's sufficiently described and ready for the team to estimate the level of effort.The product owner creates a PBI or a tester creates a bug in the New state with the default reason, New backlog item.PBIs and bugs follow this typical workflow progression: For details about creating bugs, see Manage bugs.
Use the following guidance and that provided for fields used in common across work item types when filling out the form. By defining the Business Value, product owners can specify priorities separate from the changeable backlog stack ranking. Also, by prioritizing the PBIs and bugs on the backlog page (which is captured in the Backlog Priority field), product owners can indicate which items should be given higher priority.īy defining the Effort for PBIs and bugs, teams can use the forecast feature and velocity charts to estimate future sprints or work efforts. Later, you can open each PBI or bug to provide more details and estimate the effort.
You can create PBIs and bugs from the quick add panel on the product backlog page. Typically, teams specify details only for the highest priority items, or those items assigned to the current and next sprint. As your business requirements evolve, so does your product backlog. The product owner can prioritize your product backlog based on each item's business value, effort, and relative dependency on other backlog items. When you define a product backlog item, you want to focus on the value that your customers will receive and avoid descriptions of how your team will develop the feature. Forms and guidance provided in this article reflect those available with the new form experience (Azure DevOps Services and TFS 2017 and later versions).įor guidance on the work item form for TFS 2015 or earlier versions or Visual Studio Team Explorer, see Add work items and select the earlier TFS version from the content version selector (above the table of contents). Work item tracking forms and features available to you differ depending on whether you open the form from the web portal or Visual Studio Team Explorer.