Forum Discussion
Duration vs work
Hi, I'm having trouble understanding how Project auto-calculates things. Specifically, let's say I have a task that I know will take 3 weeks of real time to happen, because it includes waiting for ...
- OlafGladAndBig,
I've found that sometimes when you're doing various scenarios and use the "undo" to back out of a step, Project goes a little "sideways". The undo command apparently is a "clean wipe" of the undone step. I don't know if you used undo in your original scenarios but that might be the "glitch".
Anyway, wait periods can be handled in various ways. One way is to create a "wait" task line with no resources assigned. Activities leading up to the wait (i.e. creating the PO, writing the order, coordination with the vendor) can be a separate task line perhaps as a predecessor to the wait task with a start-to-start + 50% (e.g. 39SS+50%). Or another common way to handle a wait time is with a lag in the predecessor where the lag itself is the wait (e.g. 39FS+2w)
John
Thank you for your response John. Apologies if my question wasn't clear.
There are six screenshots above.
1. "Order widget" with Resource Some Guy, duration 3w (Not referred to again - simply an example).
2. "Manufacture prototype with ac base". Duration 3d. Work 24h.
3. Task form for screenshot (2)
4. Screenshot (2) taken again after changing work to zero, where "fixed" duration has also been forced to zero.
5. A new task also called "Order widget" after setting work to zero where duration was not forced to zero. (the resource here is called "Wait").
6. Task form for screentshot (5).
Since these were all made-up examples, I threw in arbitrary times rather than using elapsed etc.
I can't replicate the behaviour now either, so it was either a glitch or I was doing something wrong that I'm no longer doing.
Regarding your point about resources, if you have a moment, I'd be interested to understand how you deal with a wait period. Say I order a part and have to wait 3 weeks for it; then the next task can't start until it arrives. If I put a zero-cost resource name "Wait" against that 3 week "task" then it's clear looking at the Gantt that a three week wait is happening, because it says "Wait" right there against the bar.
If you have a moment, or can point me to an explanation online, I'd be interested to know how to present a wait time.
Thanks again.
There are six screenshots above.
1. "Order widget" with Resource Some Guy, duration 3w (Not referred to again - simply an example).
2. "Manufacture prototype with ac base". Duration 3d. Work 24h.
3. Task form for screenshot (2)
4. Screenshot (2) taken again after changing work to zero, where "fixed" duration has also been forced to zero.
5. A new task also called "Order widget" after setting work to zero where duration was not forced to zero. (the resource here is called "Wait").
6. Task form for screentshot (5).
Since these were all made-up examples, I threw in arbitrary times rather than using elapsed etc.
I can't replicate the behaviour now either, so it was either a glitch or I was doing something wrong that I'm no longer doing.
Regarding your point about resources, if you have a moment, I'd be interested to understand how you deal with a wait period. Say I order a part and have to wait 3 weeks for it; then the next task can't start until it arrives. If I put a zero-cost resource name "Wait" against that 3 week "task" then it's clear looking at the Gantt that a three week wait is happening, because it says "Wait" right there against the bar.
If you have a moment, or can point me to an explanation online, I'd be interested to know how to present a wait time.
Thanks again.
OlafGladAndBig,
I've found that sometimes when you're doing various scenarios and use the "undo" to back out of a step, Project goes a little "sideways". The undo command apparently is a "clean wipe" of the undone step. I don't know if you used undo in your original scenarios but that might be the "glitch".
Anyway, wait periods can be handled in various ways. One way is to create a "wait" task line with no resources assigned. Activities leading up to the wait (i.e. creating the PO, writing the order, coordination with the vendor) can be a separate task line perhaps as a predecessor to the wait task with a start-to-start + 50% (e.g. 39SS+50%). Or another common way to handle a wait time is with a lag in the predecessor where the lag itself is the wait (e.g. 39FS+2w)
John
I've found that sometimes when you're doing various scenarios and use the "undo" to back out of a step, Project goes a little "sideways". The undo command apparently is a "clean wipe" of the undone step. I don't know if you used undo in your original scenarios but that might be the "glitch".
Anyway, wait periods can be handled in various ways. One way is to create a "wait" task line with no resources assigned. Activities leading up to the wait (i.e. creating the PO, writing the order, coordination with the vendor) can be a separate task line perhaps as a predecessor to the wait task with a start-to-start + 50% (e.g. 39SS+50%). Or another common way to handle a wait time is with a lag in the predecessor where the lag itself is the wait (e.g. 39FS+2w)
John
- Thank you - much appreciated.
- OlafGladAndBig,
You're welcome and thanks for the feedback.
John
