Racman5487 said:
Hi Julie
Yes there are constraints and predecessors, successors etc but I can't see
where these are preventing the critical path from showing correctly.
Caroline
It's a common misconception that "having links" will result in a
critical path. Not so. It will usually result in something showing as
critical, but not a true critical path. To get a correct, meaningful
critical path, you need SCHEDULE CONTINUITY. That is, every working
task has both at least one predecessor and succesor. The only
exceptions are the Start and Finish milestones you need to create to
anchor the schedule at each end and insure schedule continuity, and any
regularly scheduled meetings (usually represented as recurring tasks in
Project). Working tasks being the lowest level tasks in that part of
the outine, those with no subtasks. Summary tasks should not be linked,
partly because they can interfere with schedule continuity.
Schedule continuity is most easily seen by viewing the Network Diagram,
with the link type set to "direct", so it's clear what is linked and
what is not. If there are working tasks that have no predecessors
and/or not successors, you need to figure out what those dependencies
are. A task with no predecessors is a task that can start on day one of
the project, needs no input that is not already available. The Start
milestone is it's only predecessor. A task with no successors is a
task that is done at the end of the project, and has no other task that
needs it's output. The Finish milestone is it's only successor.
Improper use of Constrainst can also cause your CP to "dissappear".
I'll leave that to another thread.
Hope this helps in your world.