From: Jpstewar on
I note that there's a setting in Project that says, "Tasks are critical if
slack is less than or equal to 0" by default. Why would you ever want to
change this?
From: Doctor Dave on
You might work for an organisation where senior management want
forewarning of tasks that may become critical before they do so for
example so that they can take pre-emptive action.

Jpstewar wrote:
> I note that there's a setting in Project that says, "Tasks are critical if
> slack is less than or equal to 0" by default. Why would you ever want to
> change this?
From: Jim Aksel on
In my world, we have contractual requirements to provide a "Near Critical
Path" showing all those tasks with 5 days or less of Total Slack. By
definintion this includes the critical path (Total Slack=0).
--
If this post was helpful, please consider rating it.

Jim Aksel, MVP

Check out my blog for more information:
http://www.msprojectblog.com



"Doctor Dave" wrote:

> You might work for an organisation where senior management want
> forewarning of tasks that may become critical before they do so for
> example so that they can take pre-emptive action.
>
> Jpstewar wrote:
> > I note that there's a setting in Project that says, "Tasks are critical if
> > slack is less than or equal to 0" by default. Why would you ever want to
> > change this?
> .
>
From: Trevor Rabey on
It is one thing to know which tasks are critical now, but those non-critical
tasks which don't have much float (slack) will be the next most likely to
become critical if things change (they will). Having only a bit of float is
not much less critical than having no float at all.
--
Trevor Rabey
0407213955
61 8 92727485
PERFECT PROJECT PLANNING
www.perfectproject.com.au

"Jpstewar" <Jpstewar(a)discussions.microsoft.com> wrote in message
news:0E61EED2-CCCC-47F9-AFE7-56D67C124066(a)microsoft.com...
>I note that there's a setting in Project that says, "Tasks are critical if
> slack is less than or equal to 0" by default. Why would you ever want to
> change this?