Partial predecessor
in [Project]
|
Prev: Assigning task on vacation day for a specific scneario(for SF depe
Next: Adding a column...very bizarre behavior
From: Trevor Rabey on 22 Apr 2010 19:50 The bars may look like they are in the same place but this does not mean that you have produced the same result or that both produce the same model. The predecessor link and lag is a statement about a constraint. Task B cannot start until x days after Task A starts. Is not the same as Task B cannot start until y days before Task A finishes. -- Trevor Rabey 0407213955 61 8 92727485 PERFECT PROJECT PLANNING www.perfectproject.com.au "Jpstewar" <Jpstewar(a)discussions.microsoft.com> wrote in message news:EC87B576-556F-4213-8EF4-73D1A4476CF0(a)microsoft.com... >I tried these and it looks like they both have the same end result. B >starts > 25% of the way into A. So it seems moot as to whether you use F to S or S > to > S. Either way, same end result, yes? > > "Dale Howard [MVP]" wrote: > >> Jpstewar -- >> >> Link task A and task B with the default Finish-to-Start dependency. In >> the >> Gantt Chart, double-click the link line between task A and task B (it's >> the >> easiest to double-click on the arrow head at the end of the link line). >> In >> the Task Dependency dialog, select the Start-to-Start dependency and then >> enter 25% in the Lag field. Alternately, leave the Finish-to-Start >> dependency selected and enter -75% in the Lag field. In either >> situation, >> click the OK button and you have modeled the dependency relationship you >> seek. Hope this helps. >> >> -- >> Dale A. Howard [MVP] >> VP of Educational Services >> msProjectExperts >> http://www.msprojectexperts.com >> http://www.projectserverexperts.com >> "We write the books on Project Server" >> >> >> "Jpstewar" <Jpstewar(a)discussions.microsoft.com> wrote in message >> news:DC0EC490-9E83-494B-8552-0379104279FD(a)microsoft.com... >> > Scenario: Information from task A is needed for task B, which is a >> > meeting >> > (or milestone) on the project plan - think of it as task 3, the MRC >> > pre-meeting. Task A does NOT have to be finished by the time of the >> > meeting, >> > but some information is needed. We are calling A a predecessor to B, >> > but >> > maybe that is not correct. We just need information from A so let's >> > say A >> > needs to be 25% complete. Is there a way of capturing that? >> |