What it is: The critical path is the longest chain of dependent tasks that must be finished for the project to reach its completion. There is a delay within this chain of dependent tasks in this project.
Why it matters: If not addressed, a delay within this series of tasks puts the due date of the project at risk. This is because the downstream durations remain unchanged, pushing the completion date over the deadline.
In the example below there is a one day delay on the first SmartTask in the Critical Path. The original dates are shown here in Critical Path view denoted by a red "x." The Team Kickoff Meeting should have been finished on 9/30, but did not. The forecasted dates are shown below the original dates in purple. Look at the last SmartTask in the Critical Path--Revise /Finalize Q1 Plan--notice that our original completion date of 10/16 has shifted out to 10/20. This is two business days behind schedule. Without remediation our original deadline will be missed.
What's next: Choose to accept delays and the new due date of your project, or review the Critical Path to identify ways to get the project back on schedule.
Contact the owners of downstream SmartTasks to see where your durations can be shortened to bring you back within your originally forecasted timeframe. This can be done in person, or by opening up the SmartTask and sending a message to your team member via Moovila. It is also important that you reach out to the owner of the delayed SmartTask to ensure that they are aware of the delay and learn their expectation of when they will finish to mitigate any further delay.
In the example below the two business day delay was covered by shortening the duration of the second and third SmartTasks in the Critical Path. Note that we're now finishing on 10/16 as originally scheduled.