From: Diana on
How do I constrain Task 3 to start and finish as follows: Tasks 2 and 3 start
as soon as Task 1 is completed. Task 3 finishes 2 weeks after Task 2 is
completed.
I'm setting the predecessors for Task 3 as follow => 1,2FF+2 wks. Finish day
is calculated correctly but the start date moves to match the default
duration.

Thanks in advance,
Diana
From: Jim Aksel on
This is a varaiation on a Hammock task. The start is driven by 1FS and the
finish is driven by 2FF+2wks.

What would do is estblish an intermediate milestone between 2 & 3 called
"Task 3 may finish" (or something else useful). Now, hammock task 3 as start
with the finish of Task1 and Task3 finish a with the milestone.

Now task 1 completion will drive the start of task 3. Should Task2 run long
(or short) the finish of Task 3 is driven by the milestone. The mileston is
2FF+2wk.

I actually wrote a white paper about this. It is buried in a paper on my
blog about "Predecessor and Successor Relaltionships". See if that helps.

--
If this post was helpful, please consider rating it.

Jim Aksel, MVP

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



"Diana" wrote:

> How do I constrain Task 3 to start and finish as follows: Tasks 2 and 3 start
> as soon as Task 1 is completed. Task 3 finishes 2 weeks after Task 2 is
> completed.
> I'm setting the predecessors for Task 3 as follow => 1,2FF+2 wks. Finish day
> is calculated correctly but the start date moves to match the default
> duration.
>
> Thanks in advance,
> Diana
From: Diana on
Jim,

Thanks for your reply. After reading your recommendation and your paper I
tried it but still the duration doesn't update automatically. Therefore,
duration is shown as the default of 1d and the Gantt bar is not correct. In
your example on the paper the duration (9days) for the Hammock Task was the
same before and after linking the tasks. Any other suggestions?



"Jim Aksel" wrote:

> This is a varaiation on a Hammock task. The start is driven by 1FS and the
> finish is driven by 2FF+2wks.
>
> What would do is estblish an intermediate milestone between 2 & 3 called
> "Task 3 may finish" (or something else useful). Now, hammock task 3 as start
> with the finish of Task1 and Task3 finish a with the milestone.
>
> Now task 1 completion will drive the start of task 3. Should Task2 run long
> (or short) the finish of Task 3 is driven by the milestone. The mileston is
> 2FF+2wk.
>
> I actually wrote a white paper about this. It is buried in a paper on my
> blog about "Predecessor and Successor Relaltionships". See if that helps.
>
> --
> If this post was helpful, please consider rating it.
>
> Jim Aksel, MVP
>
> Check out my blog for more information:
> http://www.msprojectblog.com
>
>
>
> "Diana" wrote:
>
> > How do I constrain Task 3 to start and finish as follows: Tasks 2 and 3 start
> > as soon as Task 1 is completed. Task 3 finishes 2 weeks after Task 2 is
> > completed.
> > I'm setting the predecessors for Task 3 as follow => 1,2FF+2 wks. Finish day
> > is calculated correctly but the start date moves to match the default
> > duration.
> >
> > Thanks in advance,
> > Diana
From: Jim Aksel on
make sure there are no other constraints or predecessors on the hammock task.
Also, is calculation set to automatic?

Press F9 to recalculate. To specific automatic caclucaitons:
Tools/Options/Calculation (tab) and select automatic.

I happen to have a little time today... if you can't get it figured out, go
over to the blog and send me your contact info.
--
If this post was helpful, please consider rating it.

Jim Aksel, MVP

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



"Diana" wrote:

> Jim,
>
> Thanks for your reply. After reading your recommendation and your paper I
> tried it but still the duration doesn't update automatically. Therefore,
> duration is shown as the default of 1d and the Gantt bar is not correct. In
> your example on the paper the duration (9days) for the Hammock Task was the
> same before and after linking the tasks. Any other suggestions?
>
>
>
> "Jim Aksel" wrote:
>
> > This is a varaiation on a Hammock task. The start is driven by 1FS and the
> > finish is driven by 2FF+2wks.
> >
> > What would do is estblish an intermediate milestone between 2 & 3 called
> > "Task 3 may finish" (or something else useful). Now, hammock task 3 as start
> > with the finish of Task1 and Task3 finish a with the milestone.
> >
> > Now task 1 completion will drive the start of task 3. Should Task2 run long
> > (or short) the finish of Task 3 is driven by the milestone. The mileston is
> > 2FF+2wk.
> >
> > I actually wrote a white paper about this. It is buried in a paper on my
> > blog about "Predecessor and Successor Relaltionships". See if that helps.
> >
> > --
> > If this post was helpful, please consider rating it.
> >
> > Jim Aksel, MVP
> >
> > Check out my blog for more information:
> > http://www.msprojectblog.com
> >
> >
> >
> > "Diana" wrote:
> >
> > > How do I constrain Task 3 to start and finish as follows: Tasks 2 and 3 start
> > > as soon as Task 1 is completed. Task 3 finishes 2 weeks after Task 2 is
> > > completed.
> > > I'm setting the predecessors for Task 3 as follow => 1,2FF+2 wks. Finish day
> > > is calculated correctly but the start date moves to match the default
> > > duration.
> > >
> > > Thanks in advance,
> > > Diana