A dependency refers to a logical relationship defined as a dependency between two activities or between an activity and a milestone.
Types of Commitment
Standard dependency types are listed below. They are also standard in the system.
( For example; you created two Work Diffraction Structures as A and B respectively.)
FTS - Finish To Start : ( If there is a FTS type dependency between A and B, this means; B cannot be started before A is completed. )
STS - Start To Start : ( If there is an STS type dependency between A and B, this means that A cannot start before B starts. )
FTF - Finish To Finish : ( If there is a FTF type dependency between A and B, this means; B cannot be completed before A is finished. )
STF - Start To Finish : ( If there is an STF type dependency between A and B, this means that A cannot finish before B starts. )
Finish to Start is a natural dependency. Each previous activity will finish before the next activity(ies) can start. Whenever possible, this logical relationship should be used.
Creating Dependency Between Work Breakdown Structure Elements
After you create WBS elements in the system, you can define the dependencies between them under the "Detail" tab -> "Network Dependencies" tab of the relevant WBS.
Hint: Imagine you created three Work Breakdown Structure elements, A, B, and C, respectively.
You want to know that after A finishes, B should start, and after A finishes, C should start.
Under the "Detail" tab of WBS A; after clicking the "New" button, you can select "WBS B" as "Project Element Code" and "FTS - Finish To Start" as "Network Dependency". Similarly, you can select "WBS C" as "Project Element Code" and "FTS - Finish To Start" as "Network Dependency".
If you want, you can type "Lag Time" for each commitment.