J
John
When creating a project schedule, what is the best way to represent wait
time (time waiting for something to happen such as a contract signing or a
purchase order to process through the system)?
For instance, the actual signing of the contract will only take about 2
hours worth of work, but it might be sitting on someone's desk for 5 days.
Would I represent that as a 5 day task with 2 hours worth of work, or would
I represent that as a 1 day task (2 hours of work) with the next task having
5 days of float (between it and the previous task)?
All of the books that I've read use a cement pouring and setting example
(that the actual pouring of the cement takes 2 days but the setting of the
concrete takes 2 additional days, therefore I should artificially put slack
between the cement pouring task and the successor task).
Could someone give me some advice as to the recommended way of doing this
and the implications of each method?
Thanks
John
time (time waiting for something to happen such as a contract signing or a
purchase order to process through the system)?
For instance, the actual signing of the contract will only take about 2
hours worth of work, but it might be sitting on someone's desk for 5 days.
Would I represent that as a 5 day task with 2 hours worth of work, or would
I represent that as a 1 day task (2 hours of work) with the next task having
5 days of float (between it and the previous task)?
All of the books that I've read use a cement pouring and setting example
(that the actual pouring of the cement takes 2 days but the setting of the
concrete takes 2 additional days, therefore I should artificially put slack
between the cement pouring task and the successor task).
Could someone give me some advice as to the recommended way of doing this
and the implications of each method?
Thanks
John