What do you mean by saying the "purchase software" task has a fixed duration
of 20 days? Are you saying that once it is ordered you expect it will be
delivered in 20 days? I tend to like the idea that the task is limited to
the actual physical work. If it takes 3 hours to fill out the purchase
order and get it signed then call the software vendor and place the order,
then you wait 3 weeks for delivery and then you'll install it, the "order
software" task is not 21 days. The order task is 3 hours in duration
followed by a 21 day lag time waiting for delivery and then the installation
task. So the project plan would show "order" with a duration of 3 hours
linked FS to "install" and a 21 days lag time in the link to position the
install 3 weeks after the order is placed.
--
Steve House [MVP]
MS Project Trainer/Consultant
Visit
http://www.mvps.org/project/faqs.htm for the FAQs
beth said:
hi, if i have a task such as purchase software that has a fixed duration
of 20d, and other tasks after it are dependent on ithe software, do i assume
that this software will be bought in batches say 2 days into the duration
so that work can start off on the succeding tasks?is this assumption ideal
ideal? cause i cant think of another way out to avoid that long period of
(20d) wait.