Merge pull request #8285 from MicrosoftDocs/users/chcomley/486427-refresh-track-dependencies

Boards - refresh track-dependencies.md

Author: AnnaMHuff

docs/boards/plans/track-dependencies.md

@@ -1,91 +1,102 @@
 ---
-title: Track dependencies by using Delivery Plans in Azure Boards 
+title: Track dependencies in Delivery Plans
 titleSuffix: Azure Boards
-description: Learn how to track dependencies within teams, across teams, and across projects by using Delivery Plans in Azure Boards.
+description: Learn how to view and manage work item dependencies using dependency tracking features in Delivery Plans.
 ms.service: azure-devops-boards
 ms.custom: cross-project  
 ms.author: chcomley
 author: chcomley
 ms.topic: how-to
 monikerRange: '>= azure-devops-2022'
-ms.date: 08/03/2022
+ms.date: 09/03/2025
 ---
 
 
-# Track dependencies by using Delivery Plans 
+# Track dependencies in Delivery Plans
 
 [!INCLUDE [version-gt-eq-2022](../../includes/version-gt-eq-2022.md)] 
 
-With Delivery Plans, you can track dependencies that have been added to work items. Dependency tracking supports the **Predecessor/Successor** link type between work items. The following image shows several work items that have dependencies. Those cards with a :::image type="icon" source="media/dependencies/dependency-green-icon.png" border="false"::: green icon indicate there are no dependency issues. Those cards with a :::image type="icon" source="media/dependencies/dependency-red-icon.png" border="false"::: red icon indicate there are issues with one or more dependencies. Dependency issues arise when a predecessor work item is scheduled to finish after a successor work item. 
+Delivery Plans provide visual dependency tracking for work items linked with **Predecessor/Successor** relationships. Dependency visualization helps you identify scheduling conflicts and manage cross-team dependencies effectively.
 
-:::image type="content" source="media/dependencies/dependencies-with-without-issues.png" alt-text="Screenshot of delivery plan showing work items with dependencies and dependencies with issues.":::
+Cards display dependency status icons:
+- :::image type="icon" source="media/dependencies/dependency-green-icon.png" border="false"::: **Green icon**: No dependency scheduling issues
+- :::image type="icon" source="media/dependencies/dependency-red-icon.png" border="false"::: **Red icon**: Dependency scheduling conflicts detected
 
-To view dependencies, you must first define the Delivery Plan and dependencies between work items. To learn how, see [Add or edit a Delivery Plans](add-edit-delivery-plan.md) and [Link user stories, issues, bugs, and other work items](../backlogs/add-link.md#link-several-work-items). 
-
-> [!TIP]  
-> You can create dependencies between work items in different projects and different teams within the same organization, but not in projects in different organizations. You can open a work item and add a dependency through the links tab. 
+:::image type="content" source="media/dependencies/dependencies-with-without-issues.png" alt-text="Screenshot of delivery plan showing work items with dependencies and dependency issues.":::
 
 ## Prerequisites
 
-| Category | Requirements |
-|--------------|-------------|
-| **Permissions** | - To view a Delivery Plan: Member of the **Project Collection Valid Users** group. Users granted **Stakeholder** access for a private project can view plans. Users granted **Stakeholder** access for a public project can add and view plans.<br> - To open or modify a work item or add work items: **Edit work items in this node** permission set to **Allow** for the Area Paths assigned to the work item. |
-| **Configuration** |- For work items and dependency lines to appear on the plan: [Enable a team product or portfolio backlog](../../organizations/settings/select-backlog-navigation-levels.md) to select it for a plan.<br> - Work items belong to a team's [product backlog](../backlogs/create-your-backlog.md) or [portfolio backlog](../backlogs/define-features-epics.md). Only work items belonging to a category selected for viewing on a team's backlog and meet any [field criteria defined for the plan](add-edit-delivery-plan.md#field-criteria) appear on the plan. <br> - [Sprints selected for each team](../../organizations/settings/set-iteration-paths-sprints.md#select-team-sprints-and-set-the-default-iteration-path) defined in the plan.<br> - [Start and end dates](../../organizations/settings/set-iteration-paths-sprints.md#add-iterations-and-set-iteration-dates) defined for each project iteration.<br> - [**Iteration Paths**](../sprints/assign-work-sprint.md) or [**Start Date/Target Date**](../queries/query-by-date-or-current-iteration.md#date-and-iteration-path-fields) defined for each work item. When defined, **Start Date/Target Date** overrides the sprint assigned to a work item.<br> - To show dependency icons and lines:  [Work items](../backlogs/add-link.md) linked using **Predecessor-Successor** link type.<br> - Team expanded to view dependency icons and dependency lines. |
+| Requirement | Description |
+|-------------|-------------|
+| **Access** | Member of the **Project Collection Valid Users** group or **Stakeholder** access |
+| **Permissions** | **Edit work items in this node** permission set to **Allow** for relevant Area Paths |
+| **Configuration** | [Delivery Plan created](add-edit-delivery-plan.md) with teams and backlogs configured |
+| **Dependencies** | Work items [linked using Predecessor-Successor link type](../backlogs/add-link.md#link-several-work-items) |
 
-> [!TIP]  
-> If you edit a plan and don't see the changes you made appear in the plan, refresh your browser. A browser refresh is needed some times to trigger the updates.  
+For complete setup requirements, see [Add or edit a Delivery Plan](add-edit-delivery-plan.md#prerequisites).
 
-## Show dependency lines for a work item 
+> [!TIP]  
+> You can create dependencies between work items across different projects and teams within the same organization. Dependencies across organizations aren't supported.
 
-1. Open the Delivery Plan from **Boards** > **Delivery Plans**. 
+## View dependency lines
 
-	> [!div class="mx-imgBorder"]  
-	> ![Screenshot to Open Boards, Delivery Plans.](media/plans/open-plans.png) 
+1. Open your Delivery Plan from **Boards** > **Delivery Plans**.
 
-1. To view dependency lines for a work item, select the top or bottom of its card. To dismiss the lines, select the top or bottom of the card again, or anywhere else within the plan. 
+2. Select the top or bottom edge of a work item card to show its dependency lines. Select again or select elsewhere to hide the lines.
 
-	Dependency lines that have no issues show up as black lines. 
+   **No scheduling conflicts** (black lines):
+   :::image type="content" source="media/dependencies/dependency-lines-no-issue.png" alt-text="Screenshot of dependency lines showing no scheduling issues.":::
 
-	:::image type="content" source="media/dependencies/dependency-lines-no-issue.png" alt-text="Screenshot of dependency lines that have no issues.":::
+   **Scheduling conflicts** (red lines):
+   :::image type="content" source="media/dependencies/dependency-lines.png" alt-text="Screenshot of dependency lines showing scheduling conflicts between work items.":::
 
-	> [!TIP]    
-	> To view dependency lines across team backlogs, make sure to expand both teams.  
+   > [!TIP]    
+   > Expand both team rows to see dependency lines across teams.
 
-	Dependency lines that have issues, show up with red lines. The issues indicate that the successor work item is scheduled to end before the predecessor work item is completed.  
+3. To view conflict details, select the :::image type="icon" source="media/dependency-issue-icon.png" border="false"::: issue icon on the work item card.
 
-	:::image type="content" source="media/dependencies/dependency-lines.png" alt-text="Screenshot of dependency lines that show issues between several work items.":::
+   :::image type="content" source="media/dependencies/dependency-lines-issue-alert.png" alt-text="Screenshot showing dependency conflict details in a work item card.":::
 
-1. To view the issue, choose the :::image type="icon" source="media/dependency-issue-icon.png" border="false"::: icon. 
+## View dependency details
 
-	:::image type="content" source="media/dependencies/dependency-lines-issue-alert.png" alt-text="Screenshot of card showing dependent work items with an issue in predecessor-successor linkage.":::
+For detailed dependency information, select the dependency icon (:::image type="icon" source="media/dependencies/dependency-green-icon.png" border="false"::: or :::image type="icon" source="media/dependencies/dependency-red-icon.png" border="false":::) on any work item card.
 
-## Open the dependency summary for a work item 
+:::image type="content" source="media/dependencies/card-dependency-link.png" alt-text="Screenshot of work item card with dependency icon highlighted.":::
 
-To drill down into specific dependencies, open the Dependencies dialog for the work item. Choose the icon that indicates the work item has dependencies, either the :::image type="icon" source="media/dependencies/dependency-green-icon.png" border="false"::: green or :::image type="icon" source="media/dependencies/dependency-red-icon.png" border="false"::: red icon.  
+The Dependencies dialog shows:
+- All predecessor and successor work items
+- Dependency status and any scheduling conflicts
+- Cross-project dependencies (when applicable)
 
-For example, here we choose the link icon for a work item with dependencies to several work items within the same project and another project.   
+:::image type="content" source="media/dependencies/dependency-dialog-with-no-issues-cross-project.png" alt-text="Screenshot of Dependencies dialog showing work items with no scheduling conflicts.":::
 
-:::image type="content" source="media/dependencies/card-dependency-link.png" alt-text="Screen shot of card and link icon.":::
+## Resolve dependency conflicts
 
-The Dependencies dialog indicates that the work item has three predecessors and no issues.
+Dependency conflicts occur when a successor work item is scheduled to complete before its predecessor. These conflicts appear with red indicators in the Dependencies dialog.
 
-:::image type="content" source="media/dependencies/dependency-dialog-with-no-issues-cross-project.png" alt-text="Dependencies dialog for a work item with no issues.":::
+:::image type="content" source="media/dependencies/dependencies-cross-project.png" alt-text="Screenshot of Dependencies dialog showing scheduling conflicts with red indicators.":::
 
-## Identify dependency issues 
+**To resolve conflicts:**
 
-When conflicts arise, they are highlighted in red. These issues typically occur when a successor work item's end date is set before the predecessor work item's end date. To determine the end date, use either the **Target Date** for the work item or the **End Date** of the assigned **Iteration Path**.
+- **Review scheduling**: Check the **Target Date** or **Iteration Path** end dates for conflicting work items
+- **Adjust timing**: Modify work item dates or iteration assignments to resolve scheduling conflicts
+- **Re-evaluate dependencies**: Consider if dependency relationships are still accurate
 
-For example, the Dependencies dialog below shows that two predecessor work items are scheduled to complete before the successor work item. A red exclamation mark and red arrows indicate an issue with this dependency.
+> [!NOTE]
+> Dependency end dates are determined by either the work item's **Target Date** or the **End Date** of its assigned **Iteration Path**.
 
-When a dependency links to a work item in another project, the project information and other link relationships are displayed.
+## Best practices for dependency tracking
 
-:::image type="content" source="media/dependencies/dependencies-cross-project.png" alt-text="Dependencies dialog for a work item with dependencies-cross-project.":::
+- **Use consistent link types**: Always use Predecessor-Successor links for dependency tracking
+- **Regular review**: Check dependency status during sprint planning and reviews
+- **Cross-team coordination**: Expand team rows to visualize dependencies across teams
+- **Proactive management**: Address red dependency indicators promptly to avoid delays
 
-## Related content  
+## Related content
 
 - [Add or edit a Delivery Plan](add-edit-delivery-plan.md)
 - [Review team Delivery Plans](review-team-plans.md)
-- [Interactively filter your backlogs, boards, and plans](../backlogs/filter-backlogs-boards-plans.md)
-- [Backlogs, boards, and plans](../backlogs/backlogs-boards-plans.md)  
- 
- 
+- [Link work items](../backlogs/add-link.md)
+- [Use the Dependency Tracker extension](../extensions/dependency-tracker.md)
+- [Manage dependencies](../best-practices-agile-project-management.md#manage-dependencies)
+