The Solution Board is the ultimate tool for visualizing and resolving complex dependencies across multiple Agile Release Trains (ARTs) and different ALM systems. This guide details how to filter, create, track, and report on dependencies from this centralized view.
Key Benefits of Detailed Dependency Management
Feature | Description | Importance |
Cross-Board Dependency Creation | Quickly link Capabilities, Features, and Stories across different contributing Program Boards (ARTs) using intuitive visual tools or a powerful search function. | Essential for ensuring schedule alignment and identifying schedule risks during high-level planning. |
Roll-Up Visualization | Automatically visualizes lower-level dependencies (Feature/Story) onto the higher-level parent Capability cards. | Provides Portfolio and Solution Management with an immediate, high-level view of risk without needing to drill down. |
Reverse Dependency Identification | Instantly highlights when an item you are waiting on (Creator) is scheduled after your item (Receiver), indicating a critical scheduling conflict. | Allows planning teams to quickly renegotiate timelines or adjust scope to avoid missed commitments. |
Multi-ALM Dependency Tracking | Use Kendis-Only dependencies to link items spanning different ALM tools (e.g., Jira to Azure DevOps), centralizing tracking in one place. | Crucial for organizations operating across diverse tooling environments. |
1. Filtering and Customizing Dependency Lines
When the board becomes busy with cross-ART dependencies, the Dependency filter is your primary tool to focus your view on the most critical items.
Open the Filter: Click the Dependency button located at the top-right of the board. A filter modal will open.
Show/Hide Cards and Select Boards:
Hide Cards Without Dependencies: Check this box to clear the board and focus only on work items involved in a dependency relationship.
Select Board: Use this dropdown to scope the view, filtering dependency lines to only involve specific contributing Program Boards.
Filter by Status, Hierarchy, and Scope: Use these sections to narrow the visual scope of dependencies:
Dependency Status: Toggle between Open Dependencies (active/unresolved) and Resolved Dependencies (completed/closed).
Hierarchy Levels: Focus on dependencies defined at Capability Level, Feature Level, or Story Level
Board Scope:
Cross Board Dependencies: Show dependencies between items on different Program Boards (ARTs).
Same Board Features Dependencies: Show dependencies between items that exist within the same Program Board.
Identify Critical Dependency Indicators: These filters are essential for risk management:
Aligned Dependencies: Shows dependency lines where the Creator item is scheduled to complete before the Receiver item begins.
Overdue Dependencies: Highlights dependencies where the Creator's scheduled completion date has passed, or the items are scheduled to complete in the same iteration but haven't been resolved. This is typically shown by a Red Circular Indicator and red connecting lines on the board.
Reverse Dependencies: Highlights cases where the Creator (the item we are waiting on) is planned to be delivered in an iteration after the Receiver (our item) is scheduled to begin.
2. Interactive Dependency Indicators (The Red Circle)
The small Red Circle on a work item card is the main entry point for inspecting and creating dependencies.
Inspect Dependencies: Hovering over the Red Circle reveals three small icons (or circles) and the Create Dependency () icon. Clicking any of the three hierarchy icons will open the full Item Dependencies modal.
On Card Hover (Left Right): The icons represent Story Feature Capability dependencies.
In Modal Tabs (Left Right): The tabs within the modal are organized as Capability Feature Story.
Item Dependencies Modal: This modal shows a list of all items dependent on or being waited on by the selected item.
"Not Visible as Lines" Tab: This is a crucial tab. It displays dependencies where the linked item exists in the ALM but is not currently visible on the Solution Board. This usually means the item is not planned into an Iteration/PI or belongs to a Program Board that is not connected to this Solution Board.
Create Dependency (+): Clicking the small plus icon allows you to initiate the dependency creation process using two powerful methods:
Method 1: Interactive Dependency Creation (Drag-and-Drop)
Click the Create Dependency (+) icon on the Creator item.
The system will show a temporary shadow of the Creator card. You can move freely across the Solution Board looking for the target item.
Click the desired Receiver item on the board. The Dependencies modal will open with both items pre-populated.
Method 2: Create by Search (Versatile Item Selection)
Open the Item Dependencies modal (by clicking the Red Circle) and click the green Create by Search button (top-right).
Click the Select Target button under the Receiver section. This is used when the target item is either not visible on the board or is difficult to locate due to the planning view being very busy.
Smart Search Modal: A secondary modal opens, allowing precise filtering of items to link:
Filter by Board (Program Board/ART), Sprint (Iteration), and Item Type (Epic, Feature, Story, etc.).
Multi-Selection: You can select one or more Features or Capabilities in this list to serve as the dependency target(s). Note: A maximum of five (5) items can be selected at once.
Click Select to return to the Dependencies modal with your receiver(s) populated.
Finalizing the Dependency: After selecting the Receiver (s), complete the link in the Dependencies modal:
Select Link Type:
ALM Context: When linking items from the same ALM (e.g., Jira), link types like "blocks" and "is blocked by" are typically available. Kendis normalizes the terminology to clearly define the flow between the Creator (Predecessor) and the Receiver (Successor).
Cross-ALM Dependency: If the items belong to different ALMs, select a Kendis-Only Link Type (e.g., "Associated with," "Depends on"). This ensures tracking happens within Kendis.
Dependency Tracking and Metadata Fields: Fill out the following fields. If multiple receivers were selected, the data entered here will be applied as a bulk update to all new dependencies created:
Field | Purpose | Context |
Summary & Description | Brief title and detailed notes about the nature and purpose of the dependency. | This is crucial for quick reference on reports and in conversations. |
Status | The current state of the dependency (e.g., Accepted, Deferred, Rejected). | Used for tracking progress and filtering risks in the Centralized Dependency View. |
Raised On / Target Resolution Date | The date the dependency was created and the expected date for its completion. | Essential for identifying Overdue and Reverse Dependencies. |
Responsible / Reporter | Assigns the person accountable for tracking the dependency resolution. | Ensures clear ownership and follow-up across ARTs. |
Conversations | A text field to log comments or conversation threads related to the dependency. | Provides history and context during resolution meetings. |
3. Centralized Dependency Tracking View
This dedicated view provides management, reporting, and export capabilities beyond the visualization on the planning board.
Access: Navigate to the More dropdown (top-right of the Solution Board) and click Dependencies (icon with two interlocking cards).
Top-Level Metrics and Filters: The top section displays key metrics as clickable counters.
Total Dependencies: All dependencies visible to the current user.
Within Board / Cross Board: Filter by the scope of the link.
Overdue / Completed / Reverse: Crucial metrics for risk and health assessment.
Clickable Filters: Clicking any of these large counter numbers instantly filters the detailed list below to show the corresponding dependency items.
Advanced Filtering (More Filters): Use the More Filters dropdown (located next to Select Statuses) to refine the dependency list by any metadata field:
Selection Process: Select a field from the first dropdown (e.g., Responsible or Target Resolution Date). A second dropdown immediately appears, populated with the unique values from that field, allowing you to select one or more values to filter the list.
Detailed Dependency List and Interaction:
The list view clearly organizes dependencies by Program Board/ART.
Clarity of Flow: Kendis simplifies the display by clearly stating the relationship:
Creator (item needed) Link Type Receiver (item waiting). This clear, left-to-right flow helps users quickly understand who needs what and by when, regardless of the confusing ALM terminology.
Hover Actions: When hovering over an individual dependency in the list, interactive options appear on the right side:
Comments Icon: Access and view conversation history.
Edit Icon: Opens the full dependency modal for updates (Status, Dates, Responsible).
Delete Icon: Permanently removes the dependency link.
Bulk Dependency Actions: This feature allows rapid updates to multiple dependencies at once.
Selection Methods:
Checkbox Selection: Select individual dependencies using the checkbox on the far left of each row.
Group Selection: Select all dependencies within a single Program Board section by clicking the checkbox next to the Program Board name.
Bulk Actions Bar: Once one or more items are selected, a Bulk Actions bar appears at the bottom, containing the Edit Selected button.
Bulk Edit Modal: Clicking Edit Selected opens a modal where you can apply changes across all selected dependencies:
By default, the Status field is available for bulk update.
Adding Fields: Click + Add Another to select any other field (e.g., Target Resolution Date, Responsible, Comment) and apply a new value to all selected items simultaneously.
Detailed Cross-Reference Tables:
The primary view provides high-level tables that show dependencies between your ART and others.
Drill-Down: You can expand the Program Board names (e.g., "Web Bookstore ART - Q4 PI4") below the main table to see the exact list of dependency items that contribute to the ART's overall metric totals (e.g., Reverse Dependencies).
Exporting Options: Use the export icon on the top-right of the Dependency Tracking View to generate reports for sharing:
Export CSV / Export Excel: Download a flat file containing the dependency data.
Export Feature Dependencies Table: Export a specialized table summarizing dependency relationships by Feature.