Jack
Tue Oct 09 14:06:16 PDT 2007
I agree with John. For major sequential phases or summary tasks, creating
start and finish milestones and linking them is a good way to do it.
Resist the temptation to link summary tasks.
-Jack Dahlgren
"John" <mjensen@theriver.com> wrote in message
news:mjensen-31FEA4.13092109102007@msnews.microsoft.com...
> In article <uSobv7pCIHA.324@TK2MSFTNGP04.phx.gbl>,
> "JR Winder" <jwinder@daystarinc.com> wrote:
>
>> I have a task (dev) with a dozen sub tasks under it. I have another task
>> (test) that obviously can't begin until the dev task is complete. My
>> question is, what is the best method for adding a SF link for the test
>> task?
>>
>> 1) Do i make the dozen sub tasks predesessors of the 'test' task? or
>> 2) Do i make the dev task the predasessor of the 'test' task?
>>
>> Thanks
>
> JR,
> You first might want to read FAQ 48 - Summary Task Linking, found on our
> MVP website at,
http://www.mvps.org/project/faqs.htm.
>
> I recommend your first option - link the last development subtask
> (performance task) to the first test subtask (also a performance task).
> In lieu of linking multiple test tasks to the last development task, I
> suggest adding a test start milestone under the test summary line and
> then linking the individual test tasks to that. You could do a similar
> thing with the finish of all the development tasks.
>
> John
> Project MVP