Progressing a project

[pm9000]

Hi all,

I have marked some tasks as 100% complete, but when I try Tools,
Tracking, Update Project - I get "did not reschedule some tasks"
because of constraints.

I'm a bit confused by this "Update Project". Is it really necessary
to run this. Can't I just do a level on the project?

Many thanks,
Mark

 

[Dave]

You need to first of all bring forward any incomplete work what is
scheduled in the past on your plan. This is done by the update project
options. Then you can level.

Do you have any constraints or do you have any activities that have been
worked on in conflict with the network logic?

 

[pm9000]

Not sure what you mean by update project options.

I have unchecked Tools, Options, Schedule, "Tasks will always honor
their constraint dates"

Thing is, I have pre-project tasks - which are to begin before the
project "Start Date" but "Update Project" still complains.

I have about 2000 tasks - and don't really want to have to change the
project "Start Date".

I do have links with negative lag to pre-project tasks.

Hope that makes sense.

Mark

 

[Dave Bellamy]

Hi all,

I have marked some tasks as 100% complete, but when I try Tools,
Tracking, Update Project - I get "did not reschedule some tasks"
because of constraints.

I'm a bit confused by this "Update Project". Is it really necessary
to run this. Can't I just do a level on the project?

Many thanks,
Mark

If you have constraints that are preventing updating, they need to be
removed or the dates changed to dates that can actually be met. Then they
can be updated.
Leveling has nothing to do with updating. It is about rescheduling tasks
that have the same resources scheduled at the same time and cannot be done
simultaneously.
You want to minimize, not necessarily eliminate, constraints. Particularly
MSO, MFO, SNL, FNL constraints will cause you problems. Use these very
sparingly, if at all. There are, of course, situations where they apply, or
they wouldn't be there, but they shouldn't be used arbitrarily or
capriciously. In relality, most tasks are going to start when their
predecessors finish, regardless of what you or others may want to happen.
Don't use constraints to try to force your pre-conceptions of when the
project/task SHOULD be done.
Hope this helps in your world.

 

[pm9000]

If you have constraints that are preventing updating, they need to be
removed or the dates changed to dates that can actually be met. Then they
can be updated.
Leveling has nothing to do with updating. It is about rescheduling tasks
that have the same resources scheduled at the same time and cannot be done
simultaneously.
You want to minimize, not necessarily eliminate, constraints. Particularly
MSO, MFO, SNL, FNL constraints will cause you problems. Use these very
sparingly, if at all. There are, of course, situations where they apply, or
they wouldn't be there, but they shouldn't be used arbitrarily or
capriciously. In relality, most tasks are going to start when their
predecessors finish, regardless of what you or others may want to happen.
Don't use constraints to try to force your pre-conceptions of when the
project/task SHOULD be done.
Hope this helps in your world.

I only have three constraints, and they are all SNET.

Update Project still complains. If I remove the constraints Update
Project doesn't complain, but the dates move more into the future.

I can't see why Update Project should complain. Is my thinking right
here?

Thanks
Mark