S
Steve House
Jumping in, it seems that part of the problem is that you are trying to tell
project when the tasks will end rather than letting it tell you when the
tasks are predicted to end. Supplying a finish date always sets an FNET
constraint, by design. The solution is simple - do not supply scheduled
finish dates, Project is not designed to document your independently
arrived-at date projections. Baselines preserve the original intention but
the plan itself should be a dynamic thing, constantly updating the projected
start and ending dates for future tasks by taking into account what has come
before. When a predecessor finishes early, Project tells you the new
projected start and finish dates for future tasks so that you can tell the
resources to adjust their planned schedules. You don't tell Project the
schedule, it tells you.
project when the tasks will end rather than letting it tell you when the
tasks are predicted to end. Supplying a finish date always sets an FNET
constraint, by design. The solution is simple - do not supply scheduled
finish dates, Project is not designed to document your independently
arrived-at date projections. Baselines preserve the original intention but
the plan itself should be a dynamic thing, constantly updating the projected
start and ending dates for future tasks by taking into account what has come
before. When a predecessor finishes early, Project tells you the new
projected start and finish dates for future tasks so that you can tell the
resources to adjust their planned schedules. You don't tell Project the
schedule, it tells you.