J
JimS
I understand Total Slack, and I like to use it to identify "close" deadlines.
Recently, I was running a scheduling session, opened up a column to display
"Total Slack", and began making changes to critical tasks to alleviate their
tightness. The schedule has no resources assigned, very few constraints (I
hate them), and a fair number of subprojects heirarchically defined with
deadlines on each task. The project end date does not constrain.
When I changed the deadline on a critical task, or changed the duration, I
expected the Total Slack column to recalculate appropriately. For example, I
might move the deadline out on the sequence of tasks so as to relieve the
pressure on that sequence ("We don't need that as soon as we expected....")
What I found was that the Total Slack column did not update. It stayed the
same, no matter what we did with respect to durations or deadlines.
I expected it to adjust in real time. Why didn't it?
Recently, I was running a scheduling session, opened up a column to display
"Total Slack", and began making changes to critical tasks to alleviate their
tightness. The schedule has no resources assigned, very few constraints (I
hate them), and a fair number of subprojects heirarchically defined with
deadlines on each task. The project end date does not constrain.
When I changed the deadline on a critical task, or changed the duration, I
expected the Total Slack column to recalculate appropriately. For example, I
might move the deadline out on the sequence of tasks so as to relieve the
pressure on that sequence ("We don't need that as soon as we expected....")
What I found was that the Total Slack column did not update. It stayed the
same, no matter what we did with respect to durations or deadlines.
I expected it to adjust in real time. Why didn't it?