dspTrack
Use Dependency Types
Refer to Import Project Files into dspTrack™ for more information.
Use a dependency type (Start to Finish, Finish to Start, Finish to Finish, or Start to Start) to set when work on a dependent Plan task can start or finish based on when work on the predecessor task starts or finishes.
NOTE: If a project is imported into dspTrack™, the dependency types are automatically added in dspTrack™ and do not need to be set.
NOTE: If a project is imported into dspTrack™, and the slack value is in the form of a percent in Microsoft Project, that value will be displayed as number of days in the Slack and Slack UOM fields on the Plan Task Dependency page.
Refer to Add a Predecessor Task and Import Project Files into dspTrack™ for more information.
NOTE: Work List Items, added on the Work List Setup page, do not have predecessor tasks and do not use dependency types.
A dependent task is in the status Waiting on Dependency on the Work List until its predecessor task has started or finished based on the dependency type. Once a predecessor task has started or finished, the dependent task moves to Ready status on the Work List.
If a task on the Work List is in a status of Waiting on Dependency, when the user clicks the Next Action button, the task(s) and the dependency/dependencies that prevent the selected task from moving to the next status display.
A Plan task has started when a user clicks the Next Action button on the Work List to move the task status from Ready to In Process.
A Plan task has finished when a user clicks Next Action on the Work List to move the task status from In Progress to Completed.
Until the predecessor task is in the appropriate status based on the dependency type, the dependent task will remain in Waiting on Dependency status and work cannot start or finish for the dependent task. For example, Task A has a predecessor that has not finished, with a dependency of Finish to Finish. Work on Task A could start, but could not finish until its predecessor task has finished. In this case, if a user clicks Next Action on the Work List for a Plan task that is in Waiting on Dependency status, an error message displays.
Based on the dependency type, if work on a dependent task begins late, the dependent task will show as late on the Work List. If the dependent task is part of the critical path used by the Schedule Status feature, the critical path will show as late.
Refer to Calculate the Critical Path for a Plan for more information.
There are four dependency types.
Finish to Start
This dependency type dictates that work on the predecessor task must be finished before work on the dependent task can start.
A user clicks Next Action on the Work List to move the predecessor Plan Task from In Progress status to Completed status. The dependent task status moves from Waiting on Dependency to Ready status and work on the dependent task can begin.
When setting a Finish to Start dependency type, the planned finish date for the predecessor task must not be a later date than the planned start date for the dependent task. If the dates are not set correctly, an error message displays when saving the dependency on the Plan Task Dependency page.
Start to Finish
This dependency type dictates that work on the predecessor task must have started before work on the dependent task can finish.
A user clicks Next Action on the Work List to move the predecessor Plan Task from Ready to In Progress status. Work on the dependent task may have already begun, but the user cannot move the task status from In Progress to Completed until the predecessor task has a status of In Progress.
When setting a Start to Finish dependency type, the planned start date for the predecessor task must be earlier than the Planned finish date for the dependent task. If the dates are not set correctly, an error message displays when saving the dependency on the Plan Task Dependency page.
Start to Start
This dependency type dictates that work on the predecessor task must have started before work on the dependent task can finish.
A user clicks Next Action on the Work List to move the predecessor Plan Task from Ready to In Progress status. Work on the dependent task may have already begun, but the user cannot move the task status from In Progress to Completed until the predecessor task has a status of In Progress.
When setting a Start to Finish dependency type, the planned start date for the predecessor task must be earlier than the Planned finish date for the dependent task. If the dates are not set correctly, an error message displays when saving the dependency on the Plan Task Dependency page.
Finish to Finish
This dependency type dictates that work on the predecessor task must be finished before work on the dependent task can be finished.
A user clicks Next Action on the Work List to move the predecessor Plan Task from In Progress to Completed status. Work on the dependent task may have already begun but cannot move from In Progress to Completed status until the predecessor task is in Completed status.
When setting a Finish to Finish dependency type, the planned finish date for the predecessor task must be earlier than the planned finish date of the dependent task. If the dates are not set correctly, an error message displays when saving the dependency on the Plan Task Dependency page.
