how is critical path calculated in the plan
My understanding of "Critical path" is that the "Earliest start date" of all WIs assigned to the iteration are equal to "Latest start date" and also "Earliest finish date" are equal to "Latest finish date" according to the online Help However it seems not working that way. Please see the attached screenshots.
<Quotes from IC >
----------------
If the slack is zero, the task or activity is critical and is highlighted in the Gantt chart view. On the critical path, none of the activities have slack, that is, for all
these activities, ES=LS and EF=LF. A delay in an activity on the critical path delays the project.
<Quotes from IC >
----------------
If the slack is zero, the task or activity is critical and is highlighted in the Gantt chart view. On the critical path, none of the activities have slack, that is, for all
these activities, ES=LS and EF=LF. A delay in an activity on the critical path delays the project.
In the image below there are no constraints still all 3 tasks are marked as critical when there are 30 days left in the Iteration.
One answer
By default the work item constraint is As Soon As Possible. This means the task should be scheduled as soon as there is a free time.
This is the reason why there is no slack for the task. This is the reason why the tasks were marked as critical.
If we had supported the As Late As Possible constraint then we would have taken the iteration end date and had scheduled from reverse, even then the work items would had been critical.
One of the best way is to control the planned dates is by using the constraint dates.
This is the reason why there is no slack for the task. This is the reason why the tasks were marked as critical.
If we had supported the As Late As Possible constraint then we would have taken the iteration end date and had scheduled from reverse, even then the work items would had been critical.
One of the best way is to control the planned dates is by using the constraint dates.