Task Dependencies in the Task Tracker

Overview

Creating task dependencies in the Task Tracker allows you to define relationships between tasks and visualize the sequence in which they must be completed in order to close a project.

A dependency is the relationship between predecessor and successor tasks. By definition, the predecessor is the first task; it controls the start or end date for all related successor tasks. The successor, by contrast, is the task whose start or end date is controlled by the predecessor. Tasks may have multiple predecessors or successors.

A dependency is represented by a mixture of the WBS/row number of the predecessor task followed by the initialism for the type of dependency that you’re establishing. If you create a dependency that includes a subtask, the subtask’s WBS will include decimals. For example, if your predecessor is for task WBS 1.2, you'll know it's the second subtask for task WBS 1.

Task dependencies can also be created in the Local Gantt chart. To learn more, see the Gantt Chart Dependencies article.

Task Dependency Types

There are four types of dependencies:

• Finish to Start (FS)—The predecessor ends before the successor can begin.
• Start to Start (SS)—The predecessor begins before the successor can begin.
• Finish to Finish (FF)—The predecessor ends before the successor can end.
• Start to Finish (SF)—The predecessor begins before the successor can end.

Resolving Circular Dependencies

A dependency loop—also known as a circular dependency—is a relationship between two or more items which either directly or indirectly depend on each other. If Task A depends on Task B and Task B is also dependent on Task A, this is a dependency loop. Dependencies that are set up in that way are also not helpful because it shows that it does not matter which task is started or completed first.

A more complex dependency loop that involves subtasks—which have dependencies within Kantata OX outside of the set predecessors and successors—could be harder to identify.

In the example above, the following has happened contributed to a dependency loop:

• Set Task 2 to be dependent on Task 1.1, which is a subtask of Task 1
• Set Task 3 to be dependent on Task 2
• Set Task 1 to be dependent on Task 3

In this scenario, changing a start date or due date to Task 3 would update Task 1’s date, which would automatically update the date of Task 1.1 because it is a subtask, and so on.

In addition to not being very useful, allowing dependency loops to exist on tasks in projects and templates could cause performance issues and other problems that prevent Kantata OX from running smoothly. To prevent dependency issues from being introduced or from continuing to exist, we provide error messages in Kantata that can help you identify which tasks may be contributing to dependency loops and prevent you from experiencing further issues.

Here are a few of the error messages you may encounter:

• When adding dependencies in local Gantt
  
• When adding dependencies in Task Tracker
  
• When creating a template (in the Gantt tab)
  
• When cloning a template
  
• When applying a template to a project during project creation, in the Task Tracker, or via a Form
  

Lag and Lead

You have the option to set a Lag or Lead when creating a dependency. Lag and lead are terms used to describe the amount of time between two tasks.

Lag is the amount of time that one task must wait before the other task can begin, i.e. a delay between two tasks used to extend the amount of days between the predecessor's end date and the successor's start date. For example, if a predecessor task ends on day 2 and the successor task is set to start on day 5, a lag of 3 days could be applied to extend the gap between the two tasks. This would display as 2+3d.

Lead is the opposite of lag and is used to shorten the amount of time between the predecessor's end date and the successor's start date. For example, if a predecessor task ends on day 2 and the successor task is set to start on day 5, a lead of 3 days could be applied to reduce the gap between the two tasks. This would display as 2-3d.

Cascade Changes

With the Cascade Changes functionality, any time you establish a dependency or modify a Start and/or Due date, changes automatically roll down to dependent tasks so you don’t have to manually change the dates of all successors.

To enable Cascade Changes, select the Cascade Changes icon (“   ”) in the top-right section of the Task Tracker. When Cascade Changes is on, a gray background appears behind the button.

Cascade Changes is a member-specific setting that will vary by user. Turning the setting On or Off will not affect the behavior for other account members. If an Account Administrator would like this option to be On by default when a team member first accesses the Task Tracker, they can enable the Cascade Changes setting on the General Settings page.

How to Create a Dependency in the Task Tracker

1. In the left navigation, click Projects and then select the desired project on the Projects page.
2. In the project workspace, click the Task Tracker tab.
3. In the task list, double-click the Predecessors or Successors field in-line with the task you’re establishing the dependency for.
   Note: If you don’t see the Predecessors or Successors fields, you need to configure your columns to add them.
4. Type the WBS # of the predecessor or successor task (e.g. 1), followed by the initials for the type of dependency that you’re establishing. You can separate multiple predecessors or successors with commas (e.g. 1FS, 2FS).
   FS=Finish to Start
   SS=Start to Start
   FF=Finish to Finish
   SF=Start to Finish
   
   Note: If you don’t include a dependency type, the Finish to Start (FS) dependency type is applied by default.
5. If needed, enter the amount of lag or lead days (e.g. +3d).
6. Press enter or click outside the cell to create the dependency.
   

How to Delete a Dependency in the Task Tracker

1. In the left navigation, click Projects and then select the desired project on the Projects page.
2. In the project workspace, click the Task Tracker tab.
3. In the task list, double-click the Predecessors or Successors field in-line with the task you’re deleting the dependency for. The dependency is automatically highlighted.
   Note: If you don’t see the Predecessors or Successors fields, you need to configure your columns to add them.
4. With the dependency highlighted in the Predecessor or Successors field, hit Backspace or Delete on your keyboard and then press enter or click outside the cell. The dependency is deleted.