How to replan linked dependencies with Include/Exclude weekends

Replanning linked dependencies is a critical aspect of effective project management. It allows for flexibility, risk mitigation, and improved communication, ultimately contributing to the successful execution of complex projects.

This article will outline how to update task dependencies by using the replan functionality and the rules that apply when updating with include or exclude weekends. 

Replanning Dependencies

Dependency links are created by either attaching the start/finish, finish/start, finish/finish, stat/start point of schedule tasks, once the link is created the dependency line is draw to indicate which task is linked to which task. 

Points to consider when creating linked dependencies and the lag time between them:

• When creating dependency links between tasks you can create lags to offset successors from predecessors. 
• If you change start date & duration or change the successor (the task that has an incoming dependency) then the new date offset should become the lag, this will auto calculate as you move the task. 
• if you change start date & duration of the predecessor then the lag stays as is with its successors, and using replan will move the child based on the lags already in place. 

The following example indicates how a dependency linked (successor to a predecessor) is updated by using replan with exclude weekend on:

The project manager is currently working on migrating data to a cloud on their schedule. Completion of Cloud Migration Plan task is set as the predecessor for the Infrastructure Readiness task (the successor). The task dates (start & end dates) indicate that when the predecessor ends on the 23rd of August, the successor will begin on the 24th August.

• Accessing the predecessor's dialog, the lag days between the tasks is set to 0, so when the predecessor ends the successor will begin.

• As delays are experienced with the tasks, the predecessor is now updated to end a day later than planned originally. Effectively it'll now have an end date of the 24th August instead of the 23rd with an added day of effort.
  
  
• With the predecessor's end date updated, now the schedule is replanned by using the Replan functionality.

• Once replanned, the update moves the successor's start date to the next working day (this is based on the 0 lag day between the tasks).

Rules for Include/Exclude Weekends

Include Weekends

• When creating task dependencies, the lag is including weekend days, iso a predecessor task ending on a Friday which has a successor linked with a finish-to-start dependency, a lag of 0 will mean the successor will be scheduled for Saturday. 
• Replanning your project schedule will move all successors of schedule items that have been modified to later/earlier dates, replanned items may be scheduled to fall on weekends.

Exclude Weekends

• When creating task dependencies, the lag is taking exclude weekends into account, so a predecessor task ending on a Friday which has a successor linked with a finish-to-start dependency, a lag of 0 will mean the successor will be scheduled for the following Monday.
• Replanning your project schedule will move all successors of schedule items which have been modified to later/earlier dates

NOTE: Tasks which do not have successors or predecessors will not be affected by replanning the project.