• Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint
Share this Page URL
Help

Chapter 6. Entering Scheduling Requirements > Understanding Dependency Links

Understanding Dependency Links

It's difficult to imagine a project in which no sequencing requirements exist for at least some of the tasks. Usually, one or more tasks cannot be scheduled to start until one or more other tasks have finished. One common reason for this requirement is a task using the output generated by another task. For example, in building a house, the task Frame the Walls requires the output of the task Lay the Foundation. This relationship between tasks is known as a dependency relationship—the scheduled start or finish of one task must be set to coincide with, or to be linked to, the scheduled start or finish of another task. One of the tasks is said to be dependent on the other.

Defining Dependency Links

When tasks are linked to show a dependency relationship, the dependent task is called the successor task and the task on which its schedule depends is called its predecessor. For example, in the most common type of dependency relationship, the successor is scheduled to start as soon as the predecessor finishes.


PREVIEW

                                                                          

Not a subscriber?

Start A Free Trial


  
  • Creative Edge
  • Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint