![]() |
|
#1
|
|||
|
|||
![]()
E. Assign a deadline to the last task in the project.
|
#2
|
|||
|
|||
![]()
Thanks , two questions:
what is the difference of your answer from Choice B above? And why this is better than the other choices? |
#3
|
|||
|
|||
![]()
Choice B is a constraint, not a deadline.
Why better? Deadlines do not interrupt the scheduling engine nor change calculation of total slack. You're welcome. |
#4
|
|||
|
|||
![]() Quote:
I tried the deadline option as you suggested on a small trial schedule I have. And as you said, it did not affect the calculation of dates, however it DID influence the total slack values, for that activity and the ones coming before that activity (or its predecessors). Or did I do something wrong? |
![]() |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
flag to indicate finish date does not equal baseline finish date | TCB | Project | 3 | 08-06-2014 02:49 PM |
Assigning finish date to work with %complete | Guloluseus | Project | 3 | 12-12-2013 10:16 AM |
![]() |
ketanco | Project | 1 | 02-07-2013 06:50 AM |
![]() |
zi1 | Project | 1 | 08-04-2012 05:55 AM |
remaining duration vs finish date | ketanco | Project | 3 | 02-17-2012 02:24 PM |