Non-Critical tasks

[TinkerBell]

Can anyone tell me why Non-Critical Tasks are automatically converted to
critical tasks? After playing around in the Gantt View and Entry Table, it
has been determined that if I convert all tasks to Milestone (Non-Zero work
with resource assigned), then tasks become non-critical again. This messes
up the Gantt charts, as all tasks show up as milestones.

 

[Jim Aksel]

Tasks become critical if they have Total Slack<=0, by definition. You can
insert the Total Slack column to see the values.

The value of total slack indicating "critical" can be changed, but this is
somewhat unusual. Tools/Options.... Calculations (tab). Look at the bottom
of that window for the value. The default is 0.

By changing the duration of a task it may float onto or off of the critical
path depending on the relationship of your tasks. The critical path length
gives you the shortest possible duration of your program given the task
relationships. It is also the longest path through the network.

Perhaps I am confused on your definition as well. The standard definition
of a Milestone is a task with 0 duration, no work, no resources. It
represents a "change in state" such as "Authority to Proceed", "Contract
Complete", "Drawings Approved".

--
If this post was helpful, please consider rating it.

Jim

Visit http://project.mvps.org/ for FAQs and more information
about Microsoft Project