Does Can Do display the critical path?
Yes, the Can Do software understands the algorithm of network planning and marks critical objects in red. An planning object is considered critical when a delay in its completion would result in a delay in the project end date. For example, if the end date of a work package were delayed by 10 days, the project end date would also need to be delayed by 10 days accordingly.
The calculation is based on free and total buffer time. Free buffer time is the time by which a package can be delayed before the subsequent task is affected. Total buffer time is the time by which a task can be delayed before the project end date is affected. If the total buffer time is zero, the package is considered "critical". The sum of all critical packages is referred to as the "critical path".
In the project planner, the corresponding option for marking the critical path can be selected under View -> Representation.
In the graphically represented example, the milestone "Go-Live" is critical because the project ends simultaneously. In contrast, the "Final Report" package is not critical because there is one day of buffer time between the two objects. Therefore, the "Rework" phase is critical, as it includes a critical object.
In the example in Figure 2, the 'Final Report' package is now critical as it takes one day longer, shrinking the gap between the two objects to 0 days.
