Hi everyone
I plan to use systematically "expected finish" constraint in the following way and I wonder if one could have any warning or comment on it.
For any activity that starts, I put Actual start, and in the same time I change its Early finish into Expected finish constraint.
Before rescheduling with a new data date, I will put progress on activity.(I uncheck "link percent complete and remaining duration")
When I will reschedule the data date, the remaining duration will decrease according to the difference between first and second DD, and my activity finish date will stay the same unless expected finish falls before the second DD
The result would ideally be that the project finish date would not move when I will reschedule.
For any activity with an Expected finish constaint not completed on the second data date, I will create a filter and correct their revised expected finish date. More drastically, I could even build a Global Change to select all these less than 100% activities and change their new expected finish dates say one week after the revised Data Date.
I hope that using this procedure, I will concentrate more into fine tuning progress and logic instead of "correcting" the project to bring back the project end date where it had to be.
Note that I also plan to erase all expected finish constraints between 2 different Data Dates rescheduling in a way that regular F9 process would not be affected by this constraint.All of that being done tru Global Change procedure.
I apologize for such a long email!
Regards
Yves Trudel
I plan to use systematically "expected finish" constraint in the following way and I wonder if one could have any warning or comment on it.
For any activity that starts, I put Actual start, and in the same time I change its Early finish into Expected finish constraint.
Before rescheduling with a new data date, I will put progress on activity.(I uncheck "link percent complete and remaining duration")
When I will reschedule the data date, the remaining duration will decrease according to the difference between first and second DD, and my activity finish date will stay the same unless expected finish falls before the second DD
The result would ideally be that the project finish date would not move when I will reschedule.
For any activity with an Expected finish constaint not completed on the second data date, I will create a filter and correct their revised expected finish date. More drastically, I could even build a Global Change to select all these less than 100% activities and change their new expected finish dates say one week after the revised Data Date.
I hope that using this procedure, I will concentrate more into fine tuning progress and logic instead of "correcting" the project to bring back the project end date where it had to be.
Note that I also plan to erase all expected finish constraints between 2 different Data Dates rescheduling in a way that regular F9 process would not be affected by this constraint.All of that being done tru Global Change procedure.
I apologize for such a long email!
Regards
Yves Trudel