1. Functionality Overview
The Program Board in Kendis is a crucial tool for visualizing, creating, and managing Dependencies across Features and Stories within a Program Increment (PI). Dependencies represent critical links where one work item (Receiver or predecessor) must be completed before another item (Creator or successor) can proceed.
Core Terminology:
Receiver (Linker): The work item that must be completed first. It is the item that precedes or enables the next piece of work. It is the item that has received the request to do the dependent work. It is the predecessor.
Creator: The work item that is dependent on the Receiver. It is the item whose progress is blocked until the Receiver is finished, and is also known as the successor. The Creator is the item that establishes the dependency link and is waiting for the Receiver's completion.
It is possible for the Admin to reverse the logic to align the arrow direction with your organization's specific definition.
To access Dependency Management: You must be in the Program Board view. To see the comprehensive dashboard view, click the More button (top right menu bar) and then select Dependencies under the Tracking section.
This functionality is designed for clarity and risk management, offering flexibility in how dependencies are viewed and tracked. The dependency management feature is consistent across both Jira and Azure DevOps (ADO) integrations.
2. Key Benefits
Benefit | Description |
Clear Visibility Modes | Easily toggle between viewing comprehensive color-coded dependency lines or a simple count badge on the card, preventing board clutter while maintaining awareness. |
Instant Risk Identification | Dependency line colors (including Red for past due and Turquoise for late-resolved) instantly highlight the health and historical success of dependency resolution. |
Flexible Creation | Create dependencies using three methods: Card-to-Card Drag-and-Drop, Plus Icon Drag-and-Drop (for creating new dependent items), or Create by Search. |
Multi-Level Visualization | See dependencies at the Feature level, even if the actual link is between two child Stories. Access the granular Story view directly from the parent Feature card. |
Granular Quick-Filter | Quickly open the dependency modal, automatically filtered to show either Story-level or Feature-level dependencies using the dedicated icons on the card corner. |
List View Management | Use the List View for a global, collapsible dashboard to prioritize review based on health metrics (e.g., Overdue or Reverse Dependencies). |
Real-Time Status Updates | Update the dependency's status within the detail modal, causing the connecting line's color to change immediately and visually communicate the new status. |
3. Detailed Navigation and How-To Guide
3.1. Visualizing Dependencies (Toggling, Filtering, and Colors)
This section details how dependency lines are displayed, how to control their visibility, and what their colors signify.
3.1.1. Toggling Dependency Line Visibility
Dependency lines are shown by default but can be disabled to simplify board navigation. To change the visibility of dependency lines, click the current Board View Name (e.g., "Alicanto") in the top-right menu bar. In the "Board View" panel, toggle the Dependencies switch to the ON or OFF position.
Action | Result & Visual Cues |
Lines ON (Red Toggle) | Dependency lines connect cards across sprints/teams. |
Lines OFF (Grey Toggle) | Lines disappear, and the dependency count (e.g., a circle with "(1)") appears on the top-right corner of affected Feature cards. |
3.1.2. Board-Level Filtering (Filtering Lines on the Board)
Board-level filtering allows you to visually narrow the dependencies displayed directly on the board using quick filters.
Access Filter Panel: Click on the Search input box above the Sprint columns. The quick filter options (including Dependency Filter) will appear in the toolbar. To open the dedicated dependency filter panel on the right, click the Dependency Filter option
which expands the available options (e.g., Open, Resolved, Cross Team Dependencies).Filter by Visibility: Use the Not visible as lines filter to display dependencies where the Linker or Receiver is on the Backlog or outside the current view boundaries.
3.1.3. Quick-Filtering Dependencies on a Card
When dependency lines are off, the card corner provides specific interactive icons to view existing dependencies by type. To view the dependencies, hover over the card to see two distinct circular icons on the top-right corner:
To view Story-level dependencies: Click the leftmost circular icon (labeled, for example, '2S'). This opens the "Dependencies" modal for that card, automatically applying the Story filter to show only Story-level dependencies.
To view Feature-level dependencies: Click the rightmost circular icon (labeled, for example, '1F'). This opens the "Dependencies" modal for that card, automatically applying the Feature filter to show only Feature-level dependencies.
3.1.4. Understanding Dependency Line Colors (8 Scenarios)
The color of the dependency line is a primary visual indicator of the health, origin, and status of the relationship.
Dependency Scenario | Line Color | Meaning |
Kendis Open Dependency | Grey/Black | Active, created in Kendis, status is 'To Do' or 'In Progress'. |
ALM Open Dependency | Blue | Active, imported from Jira/ADO, status is 'To Do' or 'In Progress'. |
Kendis Resolved Dependency | Green | Completed (Kendis-Native). Status is in the 'Done' category and on track. |
ALM Resolved Dependency | Shade of Green | Completed (Imported from ALM) and on track. |
Resolved (Past Due Date) | Turquoise | Completed, but the resolution occurred after the set due date (historical schedule miss). |
Open Dependency Moved | Yellow | Active dependency where the Receiver card (the predecessor) has been moved to a different Team or Sprint. |
Open (Past Due Date) | Red | Active dependency that has missed its set due date (critical risk). |
Reverse Dependency | Red | A planning risk: the Creator (dependent item) is scheduled in an earlier sprint than the Receiver (predecessor). |
3.2. Creating New Dependencies (Three Methods)
You can create dependencies between Features and Stories using three distinct methods.
Method A: Drag-and-Drop Card-to-Card
Locate the Linker: Hover over the Feature or Story card that will be the Receiver (predecessor).
Initiate Drag: Click and drag from one of the small circles that appear on the top-right corner of the Receiver card.
Drop on Creator: Drop the line onto the top-right corner of the target Creator (successor) card.
Modal Opens: The "Dependencies" modal will open automatically, pre-populating the Receiver and Creator fields.
Method B: Drag-and-Drop to Create New Item (Plus Icon Mechanism)
This method is used when the dependent work item (Creator) has not yet been created on the board.
Initiate Drag: Drag the dependency line from the Receiver card.
Drop on Plus Icon: Drop the line onto the icon located on the top of any desired Sprint column.
Select Action: A pop-up menu will appear, asking you to choose: 'Add existing epic/bug' or 'Add new epic/bug'. Selecting 'Add new epic/bug' will open the creation modal for the new item and pre-link the dependency.
Method C: Create by Search
This method is ideal when the board is large, and the target card is not immediately visible.
Open Dependencies Modal: Click the dependency count badge on the Receiver card.
Access Search: In the top-right corner of the modal, click the green Create by Search button.
Search and Select: A search bar appears. Find and select the Creator item by its ID (key) or title.
Modal Opens: The "Dependencies" modal" will open with both items pre-populated.
3.3. Managing Dependency Details and Status
The Dependencies modal allows comprehensive management of the dependency's status, link type, and ownership. This modal can be accessed after creation or by clicking on any dependency line or count badge to open it.
Field | Purpose and Contextual Information |
Link Type | Defines the relationship (e.g., is blocked by, is cloned by). The options are grouped into Jira Link Types, Azure DevOps Link Types, and Kendis Link Types. Admin Control: A Board Admin can use Board Settings Edit Board Settings Additional Settings to Hide Kendis Dependency Link Types if only ALM links are required. |
Creator (Feature/Story) | The dependent item. Use the Feature or Story toggles above the selection box to filter the type of item you are linking to. The Creator is the dependent work item that is waiting for the Receiver to finish. Selection Aid: The items are organized by Team and Sprint to help you quickly identify the correct dependent item. |
Status | This is the state of the dependency link itself (e.g., Accepted, Waiting for Acceptance, Blocked), not the underlying work item. CRITICAL: Updating this status instantly changes the dependency line color on the board. |
Summary/Description | Required fields to clearly define what the dependency is and what steps are needed for resolution. |
Responsible/Reporter | Allows you to assign an individual who is accountable for ensuring the dependency is resolved (Responsible) and the person who created it (Reporter). |
Target Resolution Date | The date by which the dependency must be cleared to prevent impact on the Creator's schedule. |
Conversations | The Conversations area allows users to add notes and engage in discussions related to resolution. Note: This history is stored within Kendis only but is visible via the Kendis ALM extension (Jira or Azure DevOps). |
3.4. Dependency Linkage and Visualization Levels
Kendis supports multi-level dependencies and ensures visibility at the highest practical level.
Dependency Type | Visibility Behavior |
Feature-to-Feature | A direct line between two parent Feature cards. |
Story-to-Story | An aggregated line appears connecting the two parent Feature cards. To see the exact Story link, click the dropdown arrow on the Feature card to expand the Story rows. |
Unassigned ALM Features | For Features linked in the ALM but not yet assigned to a Team or Sprint in Kendis, the dependency line will display in the Phoenix View (the last delivery Sprint column for the board) to flag the item for scheduling. |
3.5. Global List View (Dependency Dashboard)
The List View provides a comprehensive, centralized dashboard for analyzing dependency health across the entire program.
Access List View: Click More in the top-right menu bar, and then click Dependencies under the Tracking section.
View Selection: The default view shows all dependencies under the All Teams selection.
Grouping Control: The two left-most dropdown menus control how the list is organized.
The first dropdown allows you to switch the view to display dependencies grouped By Receiver or By Creator.
Sequencing (1 2): When viewing the detailed dependency list, the work items are explicitly numbered to show the required flow: '1' indicates the Receiver (the item that must finish first), and '2' indicates the Creator (the item waiting).
The second dropdown acts as the Group by control, allowing you to organize the dependency list by attributes of the Features and Stories (the work items) associated with the dependency. These grouping options include standard fields (like Team or Iteration) or Custom ALM Fields linked to Kendis (Jira/ADO).
Team View: To change the entire dashboard view to focus on a single team, use the Team dropdown menu located next to the receiver filter. Selecting an individual team (e.g., Team Mars) will recalculate all metrics and display only dependencies relevant to that team.
No Value Grouping: If you select a Grouping attribute (e.g., 'Iteration') and the Feature or Story that is currently being focused on (either the Receiver or Creator, based on your top-left selection) does not have a value defined for that attribute, the dependency will be grouped under the "No Value" collapsible section. This typically means the item is unassigned in the selected field.
Filter Management and Application: The header provides advanced filtering capabilities for creating and applying focused views. Note: All filters here apply exclusively to dependencies, not to the underlying Program Board data.
Basic Filtering: Use Quick Filters, My Filters, and Instant Filters dropdowns to immediately narrow the results.
Advanced Filtering: Click the More Filters dropdown to access granular options such as filtering by:
Responsible, Creator/Receiver Team/Iteration, and Link Type.
Selecting a Filter Category (e.g., Receiver Item Type) opens a second dropdown for further refinement (e.g., choosing Feature or Story).
Execution: After selecting your criteria, click the Apply Filter button to execute the chosen criteria.
Collapsible Sections: The entire list view is organized into sections (e.g., per team) that are fully collapsible using the icon next to the section title or the Collapse All button.
Interactive Metrics: The dashboard provides high-level metrics (e.g., Total Dependencies, Overdue, Reverse Dependencies). Clicking any of these number counters will automatically filter the detailed list below to show only the dependencies matching that metric.
Program Rollup: Dependencies are categorized by team interaction to simplify risk assessment:
'1' - We Depend On: Dependencies the current team requires from other teams.
'2' - Teams Depend On Us: Dependencies that other teams require from the current team.
3.6. Admin Configuration of Dependency Logic and Arrow Directionality
The Board Admin controls the visibility logic for ALM links, the automatic status updates, and the visualization of dependency direction.
Go to Settings: Click Board Settings in the top-right menu.
Access Additional Settings: Click Edit Board Settings, then navigate to the Additional Settings tab.
Configure Dependency Arrow Direction: Locate the "Configuration for Dependency Arrow" and "Configuration for Reverse Dependency" sections.
Purpose: This setting determines how the tool interprets and visuals the direction of link types imported from your ALM (Jira/ADO), specifically defining which end is the Receiver/Predecessor (start of the arrow) and which is the Creator/Successor (end of the arrow).
Reverse Logic: It is possible for the Admin to reverse the logic to align the arrow direction with your organization's specific definition of "Outward to Inward" versus "Inward to Outward." Note: This configuration impacts how the relationship is displayed on the board (the direction of the line arrow).
Configure Auto-Update Status: Under the sections "Auto update Dependency status of Parent Item" and "Auto update Dependency status of Child Item," set the conditions under which the dependency status should update to Done. For example, you can set it to update "When Target Parent Item updates to Done."
Save: Click Save & Close.