Critical path problem

[kelly]

I just added several new tasks to my schedule. At this stage they are only
linked to each other. I have not linked them to any other tasks.
They are highlighted red showing that they are on the critical path. There
is no way they should be on the critical path.

I'm using MS project 2003

Can anyone help?

 

[Dave]

I just added several new tasks to my schedule. At this stage they are only
linked to each other. I have not linked them to any other tasks.
They are highlighted red showing that they are on the critical path. There
is no way they should be on the critical path.

I'm using MS project 2003

Can anyone help?

Are they linked to the start and end milestones?

 

[Jim Aksel]

If the tasks do not start on the first day of the project, then there is some
constraint holding them in their present location.... such action could
cause them to land on the critical path.

Examples: Long level of effort type tasks may land there.
If any of these tasks is the sole thing happening on the program at the
time, they are by definition on the critical path (vertical line test).
--
If this post was helpful, please consider rating it.

Jim

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

 

[Jack Dahlgren]

Sounds like you have project configured to calculate multiple critical
paths. When this option is set, any chain of tasks leading to a successor
with no successor becomes a critical path.

Go to tools menu / options / calculation tab. Near the bottom you see the
option to "Calculate multiple critical paths". Make sure the option is not
selected.

-Jack Dahlgren
-

 

[BillB]

MSP bases critical path on slack. I'm guessing that you have checked the
option for "Allow Multiple Critica Paths". Since those tasks are linked only
to each other, they have 0 slack, therefore they are considered critical by
MSP. Uncheck the option or connect to the start and end tasks of your
network and you'll get slack on the tasks and they'll no longer seem
critical.

Bill B