Dependencies in the Gantt view

Dependencies define the chronological relationship between tasks, milestones, and phases. This allows you to represent which planning elements must begin or be completed first and which ones follow afterwards.

In the Gantt chart, these relationships are represented by connection lines between the bars. Dependencies can be created directly in the chart and then used for further scheduling.

Dependency types in Gantt

Four standard dependency types are available in Gantt. The type that is created depends on which start or end points of the two bars are connected.

• Finish-to-Start
  The successor task can only begin once the predecessor task has been completed.
• Start-to-Start
  The start of the successor task is based on the start of the predecessor task.
• Finish-to-Finish
  The end of the successor task is based on the end of the predecessor task.
• Start-to-Finish
  The successor task can only end once the predecessor task has started.

Create a dependency graphically

Dependencies can be created directly between the task bars in Gantt.

1. Move the mouse pointer over the bar of the task from which the connection should originate.
2. The available connection points appear at the beginning and end of the bar.
3. Hold down the left mouse button at the desired connection point.
4. Drag the connection to the beginning or end of the desired target task.
5. Release the mouse button at the corresponding connection point.

The tasks are connected. The corresponding dependency type is determined automatically based on the selected start and end points.

Display dependencies on hover

Move the mouse pointer over a task to highlight its dependencies directly. The associated connection lines become visible, and an information window provides a compact overview of which tasks are linked to the selected entry.

You can distinguish between the task’s predecessors and successors:

• The entry pointing to the left shows a task that the selected task depends on.
• The entry pointing to the right shows a task that depends on the selected task.

This allows you to trace a task’s dependencies without having to open the task details.

Manage dependencies using fields

As an alternative to graphical linking, you can also manage dependencies using the task fields Blocked by and Blocks.

• Blocked by contains the predecessors that must be taken into account first.
• Blocks contains the successor tasks that depend on the current task.

Show the required fields in the task list of the Gantt chart and select the desired task or milestone in the respective cell.

Define lag and lead

A dependency can also include a time offset. This means that the successor task does not necessarily have to begin or end immediately at the linked date.

• Positive lag
  Adds a delay between the linked tasks. One example is a required waiting or drying period.
• Negative lag or lead
  Allows the successor task to begin before the predecessor has been fully completed.

Link phases and milestones

Dependencies can be created not only between regular tasks. Milestones and summary phase bars can also be linked to other planning elements.

This allows you, for example, to define that a new project phase may only begin after a previous phase has been completed or a milestone has been reached.

Show and hide dependencies

In extensive project plans, a large number of connection lines can make the view difficult to read. You can therefore show or hide dependencies using the corresponding button in the toolbar.

Even when connection lines are hidden, you can still see the dependencies of an individual task by moving the mouse pointer over the corresponding bar.

Remove a dependency

You can remove a dependency that is no longer required using the corresponding dependency fields.

1. Show the appropriate Blocked by or Blocks field in the task list.
2. Open the cell of the corresponding task.
3. Remove the link that is no longer required.

The connection line is then also removed from the Gantt chart.

Interaction between start, due date, and duration

The fields Start, Due date, and Duration are interdependent. As soon as two of these fields are filled in, the third field is calculated automatically.

When entering the values for the first time, the order in which you enter them determines which third field is calculated.

If all three fields are already filled in and one value is then changed, Duration is treated as the prioritized value:

• Start is changed: The duration remains unchanged and the due date is recalculated.
• Due date is changed: The duration remains unchanged and the start is recalculated.
• Duration is changed: The start remains unchanged and the due date is recalculated.

If you want to change the due date independently of the previous duration, you can first remove the value from the Duration field and then define a new due date.

Effects on automatic scheduling

Together with duration and possible date constraints, dependencies form the basis for automatic scheduling.

During forward or backward scheduling, smenso takes the stored relationships into account and calculates suitable start and due dates for the affected tasks.

Suggested date changes are first displayed in a preview. They are only applied to the project plan after you confirm them.