There are four different types of dependencies to link planning elements.
This type of dependency establishes a relationship between the end of the predecessor and the start of the successor. You ensure that the successor can only start upon completion of the predecessor.
Example: The activity “event marketing” can only start once the milestone “kick-off meeting“ has been successfully completed.
This type of dependency restricts the start of the successor, as it can only start once the predecessor has started, too.
Example: The successor activity “partner event program“ starts at the same time as the predecessor activity “customer event program“. That means that unless the predecessor has started, the successor cannot start.
This type of dependency restricts the end of the successor, as it can only end when, and if, the predecessor has been successfully completed.
Example: The predecessor “customer event program“ has to be completed at the latest on the end date of the successor “partner event program“, as the two programs have to be finalized for the creation of the event website.
This type of dependency is only useful if you create a work-back project plan (work-back schedule). When you create a Start-to-Finish Dependency you link the start of the predecessor with the end of the successor.
Example: If a company plans to shut down a server on a certain date and move their data to a new datacenter to consolidate the hosting, they need to make sure that the new server is up and running before they can shut down the old server. Therefore, the predecessor “full-time operation new server” needs to be completed before the successor “shut off old server” can happen.