In this article you will learn:
1. How are dates and the critical path are calculated
Task dates, project duration, and buffers are determined based on:
Dependencies in the Netplan
Fixed elements (tasks, milestones, or due dates)
Individual task durations and buffers.
The project plan is calculated backward, assigning the latest possible start date for each task or milestone to ensure timely completion. Buffer times accumulate before key points in the project, such as a milestone or project due date.
If the task chain is a secondary chain that joins the main chain (critical path), the buffers are collected before the main chain as long as there is no fixed task in the secondary chain.
The critical path represents the longest sequence of dependent tasks with the least buffer, identifying the most time-sensitive activities in the project.
2. How to ideally plan your projects
Use the AI Project Generator to set up your project plan
Use net and reserve time for the task durations to manage risks and uncertainties in your project
For optimal calculations, minimize fixed planning objects in your project plan. Keeping tasks and milestones flexible ensures the plan updates dynamically with every change.
If your project contains more than 150 planning objects, consider splitting it into separate projects and linking them.
Ensure that the final task in your project is connected to the due date (blue bar).
Tip: Get more tips on project planning here.
3. How the project data is visualized
You can switch on the critical path in the Net plan or timeline view. If multiple task chains meet the same conditions, they are all marked as critical.
The project timeline provides the best visualization of project data. It presents the entire project in a calendar view, displaying buffers and fixed elements within the project plan.
Time gaps between the calculated due date and the set due date are not shown (see example below).
Delays or scheduling conflicts are highlighted with red arrows, boxes, and smart hints in the project plan.
4. What happens during the project execution and what’s the project health
As soon as the first task of the critical chain is set to “in progress” the chain is calculated forward ensuring a successively project progress.
As the project progresses, each responsible updates the tasks and millstones, estimating the remaining days needed for completion. These updates help measure project progress and track buffer consumption. The relation between progress and buffer usage determines the project's time status: on track, at risk, or delayed.
On Track: Projects in the green zone are at ideal progress levels. The green area represents ideal project progress, while the light green corridor indicates an overly conservative plan.
At Risk: Buffer consumption and project progress are unbalanced. The project is at risk, but the due date is still achievable. To fall within the green zone, tasks must be completed, or additional buffer time should be allocated.
Delayed: The current plan will not meet the project due date. To recover, task durations must be reduced, or the due date extended.
For each week, a black dot is entered in the project health chart, representing the status of the project at that point in time. These dots are connected to form a so-called fever chart, which reflects the progress of the project.
The position of a week's dot is determined by the progress of the project during that week and the buffer consumption. This means that the position of the dot changes during the week, depending on changes in the project. At the end of the week, this status is “fixed.” The dot for the coming week is then connected to it.
The fever chart created by connecting the dots makes it easier to track the progress of the project within the project duration.
If you move the mouse over a dot in the fever chart, the week that the dot represents is displayed.
Notes:
Projects without any buffer do not have a health chart and can only have an on track or delayed status. So, they are also not included in the portfolio reporting.
Fixed elements in the project plan can be delayed. In these cases, fixed milestones or tasks retain their set dates, while their successors adjust accordingly. This ensures the overall project plan remains up to date.
