From: damien on
I would like to start a dependent task when it's predecessor reaches
something like 33% completion.

Is this something that Project can do?
From: Barbara - Austria on
Hi Damien,

yes, Project can do that for you:
Open task information of your dependent task, open Predessors tab and enter
'-67%' in 'Lag' column. Does it show what you expected?

Regards
Barbara

"damien" <damienvfx(a)gmail.com> schrieb im Newsbeitrag
news:9fe31810-1489-4d5d-9ef6-44d9b0967f64(a)11g2000yqr.googlegroups.com...
>I would like to start a dependent task when it's predecessor reaches
> something like 33% completion.
>
> Is this something that Project can do?

From: Trevor Rabey on
You can use a start-start predecessor link with positive lag or you can use
a finish-start link with negative lag, and you can specify the lag in terms
of the % of the duration of the predecessor.

Both choices are not really very good modeling, the one with the negative
lag worst of all.
FS with negative lag says that the successor cannot start until x days
before the predecessor finishes.
Or, to put it another way, the soonest that the successor can start is x
days before the predecessor finishes.
But how will you know when you are x days before the predecessor finishes.

Why not instead just chop the predecesor into two parts and use plain FS0
predecessor links?

1 Task A, 2 days
2 Task A1, 4 days, 1FS
3 Task B, 5 days, 1FS
--
Trevor Rabey
0407213955
61 8 92727485
PERFECT PROJECT PLANNING
www.perfectproject.com.au

"damien" <damienvfx(a)gmail.com> wrote in message
news:9fe31810-1489-4d5d-9ef6-44d9b0967f64(a)11g2000yqr.googlegroups.com...
>I would like to start a dependent task when it's predecessor reaches
> something like 33% completion.
>
> Is this something that Project can do?


From: Jim Aksel on
Actually, you can start the successor activity any time you want... just key
in an actual start date and forget the logic.

To schedule this propely, it is best to do it from a forward pass
(Predecessor SS+33%). Using negative lag is not a best practice since you
really don't know when the predecessor will finish with absolute certainty.

This type of planning using indicates lack of detail in the schedule. You
really should not arbitrarily say "When A is 33% complete, I can start B."
There is more than likely some tangible event in "Task A" that can be broken
out. For example, if Task is is "Mow the lawn" and Task B is "rake leaves"
..... maybe it is best to break Task A into "Mow Front Yard" and Mow Back
Yard" ... then Task B can start immediately after the front lawn is mowed.

I give an example of using % associated with Lag on my blog. Read my white
paper about Predecessor and Successor relationships.
--
If this post was helpful, please consider rating it.

Jim Aksel, MVP

Check out my blog for more information:
http://www.msprojectblog.com



"damien" wrote:

> I would like to start a dependent task when it's predecessor reaches
> something like 33% completion.
>
> Is this something that Project can do?
> .
>