Dependency Types

AdaptiveWork enables selecting from four schedule dependency types:

• Finish to Start (FtS) — The successor work item begins upon completion of the predecessor work item

• Finish to Finish (FtF) — Predecessor work item does not finish until the successor is finished

• Start to Finish (StF) — The successor work item does not finish until the predecessor starts

• Start to Start (StS) — The successor work item does not start before the predecessor starts

Adding a Dependency

1. Select a work item.

​

Figure 1: Selected Work Item

2. On the ribbon, click Add Related and then click Predecessors (or Successors).
   
   The Add Predecessors (or Add Successors ) dialog opens.​

Figure 2: Add Predecessors

3. Select and add a predecessor (or predecessors) to the Your Selections column.
4. Click the Dependency field.

​

Figure 3: Dependency Field

5. From the picklist, select the dependency type.

Figure 4: Select Dependency Type

6. Click OK to set the dependency.
7. Click OK to add the predecessor(s).
   
   The data is sent to the server.

​

Adding Multiple Work Item Dependencies

Dependencies can be added to one or more work items.

The example below describes adding dependencies to multiple work items in a Work Plan:

1. Select work items.

Figure 5: Selected Work Items

2. On the ribbon, click Add Related and then click Predecessors (or Successors).
   
   The Add Dependency dialog opens.

​Figure 2: Add Dependency

Within the dialog you can select which of the two work items will be the predecessor work item or which work item depends on the other. You can then select the dependency type, and enter the lag if relevant.

3. Select the required option.
4. Click Finish to Start (FtS), and from the drop-down menu, select the dependency type.

• (Optional) Add a lag between predecessor and successor work items

​

• To restore all manually set dates within the selected work items, and thereby allow the automatic date changes based
  on the dependency type, check the Restore checkbox.

5. Click OK
   The data is sent to the server.

Best Practices for Inter-Project Dependencies

While you can create inter-project dependencies between two completely separate projects, we do not recommend it due to possible performance issues and delays to calculations. Creating dependencies between sub-Projects in a single-hierarchy generally works better than inter-dependencies between two separate projects.

If you do create inter-project dependencies, we recommend the following best practices:

• Take into account the recalculation times, which depend on the Project size, number of resources, and the number and directions of the inter-dependencies
• Use the Process Monitor to check the performance and status of calculation jobs in the system
• Use Shortcuts to bring in the dependent items (usually tasks) into the Project hierarchy for better visibility and then easily link them with “local” items using the Link action.
  Notes:
  • When a dependency is created between items in the same project tree (“local” dependency), the system checks for a dependency loop and prevents the creation of an instant dependency if a loop is detected.
  • For an inter-Project dependency, the system cannot detect a dependency loop instantly, but rather during the recalculation process. Therefore, the system may initially allow creating an inter-Project dependency, but later on, during the recalculation process, it may detect a loop and automatically break the dependency. In such cases, the system will not recalculate the dependency, but rather display an alert in the alerts module.