New task in existing plan to start LATER

[Bryan]

My part time resource question on this group begins my thoughts in a related
area. How does one properly handle a new task in an existing project that
realistically won't start until say a week from now. I just know this based
on more info than MSP has. When I add the task, duration, and resoures it
just puts it at the begin date of the project. Leveling adds time based on
the resouce allocation. But I KNOW it won't start until weeks after project
is calculating. What's the preferred method of getting this to properly
reflect in the plan?

 

[Rod Gill]

Best option is always to link it to a task it logically has to follow and if
that is still too soon add a lag to that link. That way as your schedule
updates, the task moves at the same time.

 

[Bryan]

Thanks. That's what I do now. I was hoping for something else! This task
really isn't a successor to any particular one. When I do this, if the linked
task lags, it pushes this new task out in the schedule, and I don't really
want that to happen. In a big project, I might miss that I did that to the
task and it then doesn't get started when it needs to. The other method I've
used is to put a date constraint on it, but that has it's negatives too.

Oh well. Thanks again!

 

[Steve House [Project MVP]]

If its not truly linked as a successor to another task according to the
dictates of the process the project is following then don't force it to that
date through an arbitrary link. If it can't start until a certain date
because of availability of parts or some such, add a "Start No Earlier Than"
of its earliest possible start date. If not, then it could start today if
the resource was available. Set the option for "New Tasks Start ON..." to
"current date." That sets an SNET constraint of today when you enter the
task. Once you assign the resource to it, resource leveling will push it
out to the ealiest date it can start given the other stuff the resource also
has on his plate.

 

[Bryan]

Thanks. That option setting is helpful.

If its not truly linked as a successor to another task according to the
dictates of the process the project is following then don't force it to that
date through an arbitrary link. If it can't start until a certain date
because of availability of parts or some such, add a "Start No Earlier Than"
of its earliest possible start date. If not, then it could start today if
the resource was available. Set the option for "New Tasks Start ON..." to
"current date." That sets an SNET constraint of today when you enter the
task. Once you assign the resource to it, resource leveling will push it
out to the ealiest date it can start given the other stuff the resource also
has on his plate.