Contents:
|
|---|
...
To highlight the entire sequence, you must define dependency links between tasks. Only the strong links that impact scheduling will determine the tasks on the critical path.
Critical path is supported in Own Scope, Sub-Scope and None-Scope boxes.
Once you establish task dependencies, the App will automatically draw the Critical path.
...
| Excerpt | ||
|---|---|---|
| ||
The critical path is drawn for:
When many tasks are linked by dependencies on the critical path, and one of the tasks loses start and end dates, the critical path may be disrupted. Once the task has dates assigned again, the critical path will appear.  |
Dependency path calculation
Use strong dependenciesto determine the correct order of tasks.
The path is calculated from the end (the last task(s) in the project)
The algorithm works backward, looking for strong links connecting tasks
The most direct path (without a time gap between tasks) is highlighted
A gap between tasks is allowed only if an ASAP link has "lag time" added
...
Non-working days
The non-working days do not affect the critical path calculation. This means that if there are two tasks with a dependency on the critical path and the predecessor ends before a non-working day, the App will move the successor to start on the first working day, and both will remain on the critical path:
...
Critical Path Tab
Tasks that are a part of the critical path are listed in the Infobar > Critical Path tab.
...