So often, you are waiting on someone else to do something before you can get started on your task.
You end up sending daily check-in emails to keep updated on their progress.
Or worse, you assume they will tell you when they're done only to find out they already finished a week ago.
Hive's Dependencies app solves this problem by linking actions, so everyone knows what has to happen first. To check that it's on:
Click Apps in the left sidebar to open the App Library.
Find Dependencies and make sure its toggle is on.
When Dependencies is off, the action card's Dependencies section, the Gantt Predecessor column and the Auto-scheduling setting are hidden.
Enable Auto-scheduling in Settings
For dependencies to change the dates of linked actions, turn on auto-scheduling. If it is Off, you can still create dependencies, but they are visual links only and do not change any dates.
Workspace admins set the default for new projects in Settings > Workspace > Defaults > Auto-scheduling.
Each project can use a different setting (see Auto-scheduling options below). Project template auto-scheduling settings override the workspace default for new projects.
Adding Dependencies
There are three ways to add a dependency.
1) From an action card
Open the action that needs a dependency (it can be either the action that comes before or after).
Click the + icon next to Dependencies.
Search for the action you want to link. Actions across the workspace are listed; use the All Projects dropdown to search one project only.
Check the direction at the bottom of the dialog. This action depends on means the open action waits for the action you selected. Click the swap button to change it to Depends on this action.
Click Add.
Dependencies added from the action card are Finish-to-start with no lag. To change the type or add lag, use the Gantt chart (see Dependency types and lag).
2) On a Gantt chart
Open the project in Gantt view.
Hover over an action bar. A small circle appears at each end of the bar.
Drag from the circle at the end of one action to the circle at the start of the next action. This creates a Finish-to-start dependency.
Pro-tip: All four dependency types are supported. The circles you connect set the type: end to start (Finish-to-start), start to start (Start-to-start), end to end (Finish-to-finish), or start to end (Start-to-finish).
Lines between the bars show each dependency:
3) In the Predecessor column
In the Gantt table, type the row or WBS number of the action that comes first in the Predecessor column, for example 1.2.1. To link more than one predecessor, separate them with commas. If you don't see the column, add it from the columns icon at the top of the Gantt chart.
Dependency types and lag
To change a dependency's type or add lag time, click the dependency line in the Gantt chart. In the Edit dependency dialog:
Adjust lag time: set the number of days between the two actions. Use a negative number for lead time (overlap).
Dependency type: choose Finish to start, Start to start, Finish to finish or Start to finish.
Then click Save.
You can also write the type and lag in the Predecessor column: the predecessor number, then the type (FS, SS, FF or SF), then the lag. For example, 1.2.1FS+2d means "start 2 days after 1.2.1 finishes". A number without a type is Finish-to-start with no lag.
There are 4 types of dependencies:
Finish-to-start (FS) - You cannot start action B before action A is completed.
Use this type when one action must be finished before the next one can start.
Finish-to-finish (FF) - You cannot complete action B before action A is done.
Use this type when an action should not finish before the preceding one is completed.
Start-to-start (SS) - You cannot start action B before action A starts.
Use this type when one action must start before the next one can kick off.
Start-to-finish (SF) - You cannot complete action B before action A starts.
Use this type when an action cannot be completed until the following action starts.
Auto-scheduling options: Off, On and Strict
To avoid common scheduling issues, keep dependency structures simple and check that the auto-scheduling setting fits the project (for example, use On for flexible adjustments).
To choose how dependencies behave in a project, click the project's ⋮ menu > Edit project > Actions > Scheduling and display > Auto-scheduling, then click Save changes.
Off: Dependencies do not move when dates change. Duration and date changes to an action do not adjust other actions in the project.
On: Dependent actions are adjusted automatically when dates change. This setting favors the dependent action's start date over the dependency link itself: the preceding action can move later without affecting the dependent action until it passes the dependent action's start date. Only then does the dependent action move.
Also, if a preceding action is completed in a shorter time than planned, the dependent actions will not move earlier automatically.
Strict: Strict (or "ASAP") scheduling keeps the lead and lag time when dependencies move, so linked actions move together in either direction. If a preceding action is completed in a shorter time than planned, the dependent actions will move earlier automatically.
With Strict scheduling, make sure dependencies are set up correctly and avoid linking parent actions, especially when you work with subactions. Link the specific subactions instead to prevent conflicts.
Pro-tip: after you change the auto-scheduling setting, the project needs an update for the new setting to apply.
Managing dependencies
To see an action's dependencies, open the action. The Dependencies section shows each link relative to that action:
Waiting on [action] - this action is waiting for the other action.
[action] is waiting on this - the other action is waiting for this one.
Each row also shows the other action's due date and status. Click a row to open that action.
If the row is yellow, the other action is still open. If it is red, it is open and past its due date. If it is green, it has been completed.
Highlighting changes
When you change a date in Gantt, Hive highlights the start and due dates that changed as a result.
This makes it easier for your team, specifically project managers, to run "What if" scenarios in Gantt before taking action.
The highlight disappears when you change another date or leave the project and come back.
Alerts
If you are waiting for someone to finish something, you get a notification when they complete it, so you know you're ready to get started. The notification goes to the assignees of the dependent action and names the action that was completed and the dependency type.
Removing dependencies
There are two ways to remove a dependency.
From the action card
Open the action with the dependency you want to remove.
Hover over the dependency in the Dependencies section.
Click the X (Remove link).
From the Gantt chart
Open the project in Gantt view.
Click the line of the dependency you want to remove.
In the Edit dependency dialog, click Remove dependency link.
