Kendis provides a highly visual and intuitive way to create, manage, and track dependencies, which are critical for effective coordination across Agile Release Trains (ARTs) and teams.
What is Dependency in Kendis?
A dependency signifies that one work item (Feature or Story) cannot be completed until another specific work item is finished. Kendis enhances this relationship by adding specific attributes for better tracking and risk management.
Key Attributes of a Dependency
Attribute | Description |
Dependency Line | A visual line on the board showing the direction of the flow. |
From (The Predecessor) | The card that must be completed first (the dependent item). |
To (The Successor) | The card that requires the predecessor to be completed before it can start or finish. |
Description | A field to clearly detail the nature of the dependency and the action needed to resolve it. |
Status | Tracks the resolution state using a granular set of statuses (see table below). |
Teams | Dependencies show the teams involved (Predecessor Team and Successor Team), facilitating cross-team communication. Kendis supports dependencies within the same team as well. |
Sprints | Dependencies indicate the planned sprints for both the predecessor and successor cards, which is essential for identifying scheduling risks. Kendis supports dependencies within the same sprint as well. |
Dependency Status
Kendis now uses a rich set of statuses, each color-coded for quick visual tracking on the board.
Status | Color | Category | Description |
Done | Green | Resolved | Dependency has been completed and resolved. |
Done with Acceptance | Green | Resolved | Dependency is complete and the acceptance criteria have been met. |
In Progress | Blue | Active | Work is currently being done on the dependency. |
Accepted | Orange | Active | The dependency has been formally agreed upon and is scheduled. |
Waiting for Acceptance | Orange | Active | Dependency work is complete or ready, but pending final acceptance/verification. |
Not Started | Orange | Planning | The work to resolve the dependency has not yet begun. |
Integrated | Dark Red/ Maroon | Blocked/At Risk | The dependency has been integrated into the system, but often implies a high-risk or final stage before full closure. |
Blocked | Dark Red/ Maroon | Blocked/At Risk | An external factor is preventing the dependency from moving forward. |
Ignored | Dark Red/ Maroon | Blocked/At Risk | The dependency is being actively ignored or deprioritized (high risk). |
How to Create Dependency
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.
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). |
See How it Works
