Do this before that.
I can’t do this until you finish that.
This, then that.
These are all examples of dependencies.
When it comes to project management, a dependency is a relationship between two tasks where one stage of the workflow can’t begin until others have ended.
Generally speaking, two dependent tasks can’t be started or worked on at the same time.
In this article, we’ll explore several types of dependencies, share what staging-mondaycomblog.kinsta.cloud thinks about dependencies, and provide some examples of how to best manage dependencies (spoiler alert: automations).
What are the various types of project management dependencies?
When we think about “traditional” dependencies, we normally are referring to “finish to start” type dependencies.
But there are more!
Here are a few of them, using tasks “A” and “B” as examples.
- Finish to start: B can’t start until A has finished
- Finish to finish: B can’t finish before A is finished
- Start to start: B can’t start until A has started
- Start to finish: B can’t finish until A has started
Again, “finish to start” is the most common, or “natural,” type of task dependency. And it’s logical if you think about it. Start A, finish A. Then, start B, finish B.
The other three types of dependencies are rarely used, and if so under very special circumstances.
In addition to the above four dependencies, we can also add the following five dependency types:
Causal dependency: This dependency is a form of the “finish to start” in which one task can’t begin until the other has ended.
Example: publishing a new website. Consider the following steps:
- Buy website domain
- Change nameservers
- Create content
- Publish final website
- Promote new website via email and social channels
Clearly, you cannot publish a website (#4) until you have purchased the domain (#1) and you can’t change nameservers (#2) until you own the actual website (#1). These would be causal dependencies.
External dependency: These are dependencies that cannot be controlled by the internal project management team as they rely on others (3rd parties) to complete.
Example: The approval process. Let’s say you’ve hired a freelance writer to draft some blog posts. While you may have an internal schedule, you still have to wait for the freelancer to submit the draft for your review!
Cross-team dependency: These are dependencies that exist within an organization when one team is waiting on another team to move forward.
Example: Launching a new product. The product is done and ready to be delivered to the market; however, the product team is waiting on (dependent!) the C-suite to approve the messaging.
TL;DR: Most dependencies are of the finish to start, causal type — one task can’t begin until the other has ended.
Quick aside: What is the difference between constraints and dependencies?
Constraints and dependencies are sometimes used interchangeably, and while the two terms are related, they are not necessarily the same.
As mentioned above: a dependency is a relationship between two tasks where one stage of the workflow can’t “begin” until others have ended.
A constraint is a limitation or restriction or a boundary — usually defined and detailed by the project manager.
The three most common constraints are time, cost, and scope:
- A project has to be completed within a certain time period
- Most projects have a defined cost associated with them
- Projects should include a scope — the work that needs to get done to successfully finish a project.
Project dependencies can occur due to specific constraints, but that is not always the case.
And now, back to dependencies.
The staging-mondaycomblog.kinsta.cloud take on dependencies
Generally speaking, we are not huge fans of dependencies here at staging-mondaycomblog.kinsta.cloud
We try to avoid them if at all possible.
Dependencies tend to create bottlenecks. And bottlenecks mean waiting on other people to finish their work. Waiting on other people means you can’t move forward. You are stuck.
We encourage teams to push forward and prevent dependencies by working in parallel whenever possible.
HOWEVER … if you must include dependencies in your project management solution, consider automating the entire process.
Here is how we do it.
How staging-mondaycomblog.kinsta.cloud recommends managing dependencies
In some projects, dependencies are nearly impossible to avoid.
Either the way the project is set up or the types of activities that a project entails — dependencies are a forgone conclusion.
Thankfully, staging-mondaycomblog.kinsta.cloud has you covered.
The staging-mondaycomblog.kinsta.cloud dependency column creates vital connections between items that will help to better manage projects. In this article, we show (video) and step through (in writing with pictures) how to set dependencies and automate them.
Here is what a dependency diagram could look like in staging-mondaycomblog.kinsta.cloud
Setting up the dependencies is pretty straightforward. The real fun comes in when you can automate the process.
We add automations to ensure dependent items never start before the item it is dependent on. And, for the most part, we can “set and forget” these automations.
Bonus: You can view dependency automations both visually and in written format, as seen here:
The staging-mondaycomblog.kinsta.cloud Automations Center has what we call “dependency recipes” to get you started
Time to try staging-mondaycomblog.kinsta.cloud
Not only does staging-mondaycomblog.kinsta.cloud make it easy for you to automate dependencies, but our Work OS also provides one platform to enable better teamwork.
Learn how over 100,000 teams get work done with staging-mondaycomblog.kinsta.cloud.
Get started immediately with hundreds of visual, customizable templates or create your own. Sign up today.
Get started