LeanKit’s step-by-step guide on how to visualize dependencies and coupled work.
What are dependencies?
Any work that requires other work to be completed, or is required for other work to be completed, is part of a dependency. This might be work that has to be completed in a sequential order or work that requires other members of your team, or other teams, to complete steps in a process before other steps can proceed.
How do I visualize dependencies in LeanKit?
You can visualize both simple and complex dependencies in LeanKit.
Visualize Simple Dependencies
Simple dependencies imply a one-to-one relationship. Your work might simply need to be completed in sequential order, for example, without steps branching off or multiple steps having to be completed prior to other steps. Simple dependencies map from one step to the next. Take a look at this video to learn more about how we recommend representing these simple dependencies in LeanKit:
Visualize Complex Dependencies
Sometimes, however, the dependency relationship between work items is more complex. For example, one piece of work might require that multiple other steps be completed before and/or after it. This requires more elaborate dependency mapping to properly visualize, but it’s possible to represent these kinds of dependencies in LeanKit.
To better understand how we recommend showing complex dependencies in LeanKit, we’ll use the following example:
Imagine you have one piece of work, represented by a LeanKit card, that cannot start until three other cards are done. Additionally, three other pieces of work cannot start until this card is done. So there are three cards that this card is reliant on and three cards that are reliant on this card.
To better visualize these cards, you need a way to expressly filter the board for the cards involved in this workflow. The way we recommend doing so is by using the Internal Card ID along with tags.
So, in this example, you would enable the Internal Card ID so that each individual card on your board has displays a unique card ID.
Then, we recommend using these unique IDs in various tags within dependent cards alongside additional text indicating the type of dependency.
If a card must be preceded by one or more other cards, you might use a tag consisting of "preceded by" and the card ID of the card that must be completed before work on this one can commence. For example, you could add the tag "preceded by 12345678" to a card that can't be started on until the card 12345678 is done.
You can use a similar tag on a card to indicate which other cards depend on this card being completed first. For example, adding the tag "succeeded by 24680135" to show that card 24680135 is waiting on this card to be completed first.
You can easily copy the card ID from the card link in your browser while in the card. The final string of numbers in the URL for the card is the card ID. For example, if the link is:
you would simply copy the last set of numbers, in this case “1234567893,” to include in your tags.
Using these tags in conjunction with one another can help to point out different relationships between dependent cards. Once dependencies are tagged in this way, you will be able to filter for these tags to visualize the dependencies.
You can use the Filter using “and” or Filter using “or” checkboxes to select whether to view only cards that have all the tags you’ve included (“and”), or whether to view all cards that have any of the tags you’ve included (“or”).
This will allow you to view cards with complex relationships so that you and your team can visualize all coupled work.
Doc ID: 1192354113