Re: Lag / Lead Time

Just a point to ponder ... if the work only requires 7.2 hours of actual work (how do you estimate work that precisely, anyway? That's 3% accuracy!) why are you letting the resource have 10 times that length of time it which to do it? As PM you should be calling the shots - go to that resource at tell them "It looks like everything will be ready for you to start that task Tuesday afternoon or first thing Wednesday morning so can I count on you having it finished by the end of the day Wednesday?" Now it could be that there are other things on the resource's plate that mean it'll take him longer and of course consult with him so as to take that into account, but my suggestion is to stop thinking in terms of windows of opportunity and instead focus on how soon you can get your resources to finish the work. As Larry the Cable Guy says, "Just git 'er done."
--
Steve House [Project MVP]
MS Project Trainer & Consultant
Visit http://www.mvps.org/project/faqs.htm for the FAQs


"JR Winder" <jwinder@xxxxxxxxxxxxxx> wrote in message news:epBxWUe2HHA.140@xxxxxxxxxxxxxxxxxxxxxxx
I have a task (A) that will require 7.2 hours of work but is not estimated to finish for 10 days. Another task (B) has a FS link to task A.

My questions pertains to the best way to account for the estimated 10 days it will require task A to complete.

Should task B have a FS+10 days lag time? Or am I better off putting a constraint type of "Finish No Later Than" on task A.

Right now I have task B linked to A with a FS+10 Days, What prompted my question is that task A is scheduled to start on 8/10/07 and end on 8/11/07 (7.2hrs), when in reality it isn't estimated to end until 8/24/07.

Thanks in advance for your assistance.

JR


.