Hi,
I want to get further information re "critical path".
I still don't understand how it works and what it does for our program.
I manage a program in Clarizen under OPML, the program name is Multistakeholder Forestry Progamme, and it consists of some tasks (with sub-taks) and some milestones.
The "critical path" sign appeared in some of the tasks one day, and the next day it disappeared - but appeared in some other tasks, and again, and again. I am confused with how the "critical path" works.
Kindly explain this to me so I have the understanding when having to explain it to my colleagues.
Thanks,
Juairia Sidabutar
Please sign in to leave a comment.
Juairia,
The critical path is defined as tasks that have 0 slack, meaning if those tasks are delayed it will push back the entire project. The calculation cannot be customized, but by changing the schedule you can determine which items are on the critical path.
Can I know which items have low slack?
If a task has only one slack, it is important that I know it, no?