In project scheduling, what is the dependency type where one task must finish before the next can start?

In project scheduling, what is the dependency type where one task must finish before the next can start?

• A. Lag
• B. Reprogramming Action
• C. Finish-to-Start Relationship
• D. Supplemental Agreement

Answer: (C)

Finish-to-start is the way to ensure proper sequencing: the next task cannot begin until the previous one finishes. This is the standard dependency used in most project schedules, forming the basic link in the network that defines the order of activities and allows calculation of early/late start and finish times and the critical path. For example, you must complete the design before you can start prototyping. A lag would introduce a delay after the first task’s finish before the second starts, which is a modification of the timing, not the fundamental relationship type. The other terms refer to actions or documents outside the sequencing of tasks.

Finish-to-start is the way to ensure proper sequencing: the next task cannot begin until the previous one finishes. This is the standard dependency used in most project schedules, forming the basic link in the network that defines the order of activities and allows calculation of early/late start and finish times and the critical path. For example, you must complete the design before you can start prototyping. A lag would introduce a delay after the first task’s finish before the second starts, which is a modification of the timing, not the fundamental relationship type. The other terms refer to actions or documents outside the sequencing of tasks.