• Dependencies are timing relationships between tasks that allow you to create a project schedule that can adjust and adapt as timing changes occur.
• There are four types of dependency relationship: start-to-finish, finish-to-start, finish-to-finish, and start-to-start. Each can be further modified to contain lag or lead time.
• You should keep dependency relationships simple and to a minimum so you and those reviewing your plan can easily see what is driving the project timing.
• Critical path is the longest series of tasks that must occur on time in order for the project to finish on time. You can view critical path with filters.
• Every project must include slack to provide for inevitable delays. Slack can be added by creating a slack task or by padding the durations of tasks.
• Tasks have natural timing relationships between them that help to determine the overall timing of your project.
• Dependencies allow a project to be more flexible; they allow you to update the entire schedule automatically with a single task date change.
• You should not establish more dependencies than are necessary to create the logical flow of your project.
• Including slack in the form of lag or lead time in your schedule allows you to accommodate delays that come up over the life of the project.