Merge pull request #4721 from MicrosoftDocs/users/kaelli/dependency-t…

…racker-extension

updates to remove reference to Dependency Tracker extension.

docs/boards/best-practices-agile-project-management.md

@@ -8,7 +8,7 @@ ms.custom: cross-project
 ms.author: kaelli
 author: KathrynEE
 monikerRange: '<= azure-devops' 
-ms.date: 07/09/2021  
+ms.date: 06/02/2022 
 ---
 
 
@@ -42,7 +42,7 @@ In this article, we make the following suggestions and guidance:
 
 ## Configure your teams   
 
-Azure Boards provides each team a set of Agile tools to plan and track work. Each project defines a default team, which you can start using immediately. However, if you have a number of development or feature teams, we recommend that you define a team in Azure DevOps for each feature team. This way, each team can work autonomously while collaborating with each other. 
+Azure Boards provides each team a set of Agile tools to plan and track work. Each project defines a default team, which you can start using immediately. However, if you have several development or feature teams, we recommend that you define a team in Azure DevOps for each feature team. This way, each team can work autonomously while collaborating with each other. 
 
 #### Best practice tips: 
 
@@ -152,13 +152,15 @@ Periodically review each backlog to perform these tasks:
 - Make sure features and requirements are sized appropriately
 - Define the acceptance criteria and the definition of done for features and work 
 - Map unmapped work to Features 
+- Set your view options to support the backlog tasks you want to accomplish
 - Forecast your backlog  
 
 #### To learn how: 
 
 - [Refine your backlog](backlogs/best-practices-product-backlog.md) 
 - [Define features and epics](backlogs/define-features-epics.md)  
 - [Create your backlog](backlogs/create-your-backlog.md)  
+- [Configure your backlog view](backlogs/configure-your-backlog-view.md)  
 - [Forecast your product backlog](sprints/forecast.md)  
 
 
@@ -242,7 +244,7 @@ In Microsoft Project, you manage tasks that depend on the completion of other ta
 
 ### Add link dialog
 
-Azure Boards supports a number of link types to track related work. Choose the Predecessor/Successor link types to track work with dependencies. The quickest way to add a number of these links is to add a tag to work items that participate in producing or consuming dependencies, create a query based on this tag, and then add the required links from the triage mode of the query results. 
+Azure Boards supports many link types to track related work. Choose the **Predecessor/Successor** link types to track work with dependencies. A quick way to link work items is to add a tag to work items that participate in producing or consuming dependencies, create a query based on this tag, and then add the required links from the [triage mode of the query results](queries/triage-work-items.md). 
 
 The following Add link dialog illustrates how two work items are linked using the Successor link type. 
 
@@ -279,8 +281,8 @@ Azure Boards doesn't provide a native view of the critical path. In part, as Agi
 - Add a `dependency` tag to work items participating in dependency management
 - Use **Predecessor/Successor** link types to track dependencies of work owned by other teams or within other projects
 - Create queries to track, add, and triage dependencies 
-- Use the [Dependency Tracker](https://marketplace.visualstudio.com/items?itemName=ms-eswm.dependencytracker) Marketplace extension to view work that you have dependencies on from other teams 
-- Use the [Work Item Visualization](https://marketplace.visualstudio.com/items?itemName=ms-devlabs.WorkItemVisualization) Marketplace extension to visualize dependencies 
+- Use [Delivery Plans](plans/track-dependencies.md) to view work that you have dependencies on from other teams 
+- Use the [Work Item Visualization](https://marketplace.visualstudio.com/items?itemName=ms-devlabs.WorkItemVisualization) Marketplace extension to visualize dependencies for a specific work item within the work item form.
 
 > [!NOTE]   
 > Marketplace extensions are not supported features of Azure Boards and therefore not supported by the product team. For questions, suggestions, or issues you have when using these extensions, visit their corresponding extension page. 
@@ -289,7 +291,7 @@ Azure Boards doesn't provide a native view of the critical path. In part, as Agi
 
 - [Link user stories, issues, bugs, and other work items](backlogs/add-link.md) 
 - [Triage work items](queries/triage-work-items.md) 
-- [Plan and track dependencies using the Dependency Tracker](extensions/dependency-tracker.md)
+- [Track dependencies by using Delivery Plans](plans/track-dependencies.md)
 
 
 ## Work in sprints   

docs/boards/configure-customize.md

@@ -8,7 +8,7 @@ ms.assetid:
 ms.author: kaelli
 author: KathrynEE
 monikerRange: '<= azure-devops'
-ms.date: 05/18/2021
+ms.date: 06/02/2022 
 ---
 
 
@@ -112,7 +112,7 @@ One of the main choices teams have is choosing the work item types they use to t
      - Conduct daily scrums, update and monitor task status: [Sprint Taskboard](sprints/task-board.md)  
      - Estimate work: [Define Story Points, Effort, or Size](backlogs/create-your-backlog.md#add-details-and-estimates-to-backlog-items)
      - View progress bars, counts, or sums of rollup on tasks: [Rollup](backlogs/display-rollup.md)  
-     - Track dependencies across teams and projects: [Dependency Tracker](extensions/dependency-tracker.md)  
+     - Track dependencies across teams and projects: [Delivery Plans](plans/track-dependencies.md)  
 
      Many teams start out using Scrum methods to track and plan their work using the tools available through the Sprints hub. The Sprints tools support estimating and tracking remaining work and use of capacity planning. If you don't plan on using these tools, then adding child-dependent tasks is optional. Developers might add them simply as a checklist of items they need to complete a user story or backlog requirement. 
    :::column-end:::
@@ -130,7 +130,7 @@ One of the main choices teams have is choosing the work item types they use to t
       - Forecast sprints using team velocity: [Forecast](sprints/forecast.md)  
       - Monitor sprint burndown based on requirement estimates: [Sprint burndown](../report/dashboards/configure-sprint-burndown.md?bc=%252fazure%252fdevops%252fboards%252fbreadcrumb%252ftoc.json&toc=%252fazure%252fdevops%252fboards%252ftoc.json)  
       - Update requirement status: [Kanban board](boards/kanban-quickstart.md)  
-      - Track dependencies across teams and projects: [Dependency Tracker](extensions/dependency-tracker.md)
+      - Track dependencies across teams and projects: [Delivery Plans](plans/track-dependencies.md)  
    :::column-end:::
 :::row-end:::
 :::row:::
@@ -147,7 +147,7 @@ One of the main choices teams have is choosing the work item types they use to t
       - View calendar view of all team features: [Feature Timeline](https://marketplace.visualstudio.com/items?itemName=ms-devlabs.workitem-feature-timeline-extension)  
       - View calendar view of a specific epic: [Epic Roadmap](https://marketplace.visualstudio.com/items?itemName=ms-devlabs.workitem-feature-timeline-extension)  
       - View progress bars, counts, or sums of rollup on child items: [Rollup](backlogs/display-rollup.md)  
-      - Track dependencies across teams and projects:[Dependency Tracker](extensions/dependency-tracker.md)  
+      - Track dependencies across teams and projects: [Delivery Plans](plans/track-dependencies.md)  
    :::column-end:::
 :::row-end:::
 
@@ -191,44 +191,31 @@ The following table indicates the areas you can configure and customize and the
 
    :::column-end:::
    :::column span="1":::
-
-
    - Delivery plans
    - Feature timeline
    - Epic Roadmap
    - Portfolio plans (Beta)
-   - Dependency Tracker
-
    :::column-end:::
 :::row-end:::
 :::row:::
    :::column span="1":::
    [Iteration paths, project configuration, and team subscription](#iteration-path) (Project, Team)
    :::column-end:::
    :::column span="1":::
-
-
    - Backlogs>Sprint planning
    - Sprints>Sprint backlogs
    - Sprints>Sprint capacity
    - Sprints>Taskboard
    :::column-end:::
    :::column span="1":::
-
-
    - Velocity
    - Burndown trend 
-
    :::column-end:::
    :::column span="1":::
-
-
    - Delivery plans
    - Feature timeline
    - Epic Roadmap
    - Portfolio plans (Beta)
-   - Dependency Tracker
-
    :::column-end:::
 :::row-end:::
 :::row:::
@@ -238,43 +225,30 @@ The following table indicates the areas you can configure and customize and the
    Custom work item types, Taskboard (Process)
    :::column-end:::
    :::column span="1":::
-
-
    - Boards>Product board
    - Backlogs>Product backlog
    - Backlogs> Mapping tool
    - Sprints>Sprint backlogs
    - Sprints>Taskboard
    :::column-end:::
    :::column span="1":::
-
-
    - Velocity
-
    :::column-end:::
    :::column span="1":::
-
    :::column-end:::
 :::row-end:::
 :::row:::
    :::column span="1":::
-
    Custom work item types, Portfolio backlog (Process)  
    Additional portfolio backlogs (Process)
    :::column-end:::
    :::column span="1":::
-
-
    - Boards>Portfolio boards
    - Backlogs>Portfolio backlogs
    - Backlogs> Mapping tool
-
    :::column-end:::
    :::column span="1":::
-
-
    - Velocity
-
    :::column-end:::
    :::column span="1":::
 
@@ -294,16 +268,9 @@ The following table indicates the areas you can configure and customize and the
 
    :::column-end:::
    :::column span="1":::
-
-
    - Cumulative flow diagram
-
    :::column-end:::
    :::column span="1":::
-
-
-   - Dependency Tracker
-
    :::column-end:::
 :::row-end:::
 :::row:::
@@ -312,11 +279,8 @@ The following table indicates the areas you can configure and customize and the
    Custom field (Process)
    :::column-end:::
    :::column span="1":::
-
-
    - Boards>Product board
    - Boards>Portfolio boards
-
    :::column-end:::
    :::column span="1":::
 
@@ -355,7 +319,7 @@ A default team and default area path are defined for each project. For small tea
 Here is an example of area paths and their assignment to teams, which support portfolio management views for the Account Management and Service Delivery teams. 
 
 > [!div class="mx-imgBorder"] 
-> ![Area paths and team assignments](media/config-custom/area-path-team-assignments.png)  
+> ![Screenshot of Area paths and team assignments.](media/config-custom/area-path-team-assignments.png)  
 
 - You create hierarchical area paths to support sub categories of features and product areas 
 - To provide portfolio views, you assign two or more area paths and include sub-areas to a portfolio management team 
@@ -420,14 +384,14 @@ Rollup columns allow you to view progress bars or totals of numeric fields or de
 Here we show **Progress by all Work Items** which displays progress bars for ascendant work items based on the percentage of descendant items that have been closed. 
 
 > [!div class="mx-imgBorder"]  
-> ![Progress bars showing rollup by work items](media/config-custom/progress-by-work-items.png)  
+> ![Screenshot of backlog, Progress bars showing rollup by work items.](media/config-custom/progress-by-work-items.png)  
 
 ::: moniker range="azure-devops"
 
 In addition, the new [Delivery Plans](plans/review-team-plans.md) supports rollup views of epics, features, and other custom portfolio backlogs. 
 
 > [!div class="mx-imgBorder"]  
-> ![Screenshot showing Delivery Plans Progress rollup view of four scenarios. ](plans/media/plans/rollup-view.png)  
+> ![Screenshot showing Delivery Plans Progress rollup view of four scenarios.](plans/media/plans/rollup-view.png)  
 
 ::: moniker-end
 
@@ -445,7 +409,7 @@ Iteration paths support Scrum and Scrumban processes where work is assigned to a
 Iteration paths can be a simple flat list, or grouped under release milestones as shown in the following image. 
 
 > [!div class="mx-imgBorder"]  
-> ![Iteration paths, grouped](media/config-custom/iteration-paths-flat-or-grouped.png)  
+> ![Screenshot of Iteration paths, grouped.](media/config-custom/iteration-paths-flat-or-grouped.png)  
 
 > [!NOTE]   
 > While Iteration Paths don't impact Kanban board tools, you can use Iteration Paths as a filter on boards. To learn more, see [Filter your Kanban board](./backlogs/filter-backlogs-boards-plans.md).
@@ -512,7 +476,7 @@ Sometimes, teams want to track the status of their work that go beyond these def
 Both workflow states and Kanban columns appear in the Cumulative Flow diagram for a team. Individuals can choose which columns appear in the chart. 
 
 > [!div class="mx-imgBorder"]  
-> ![Cumulative flow diagram](media/config-custom/cumulative-flow-diagram.png)  
+> ![Screenshot of Cumulative flow diagram.](media/config-custom/cumulative-flow-diagram.png)  
 
 To learn more, see [Cumulative flow diagram](../report/dashboards/cumulative-flow.md).