If a project is generally running according to plan and activities are not progressed out of sequence then there will be virtually no difference between the two methods. BIG differences come when activities are progressed out of sequence.
Most of the time, or at least as a starting point, I believe in retained logic. Invariably that will produce the longest critical path but if activities have been progressed out of sequence, there could be some resulting illogical dependencies remaining, in particular resulting from dependencies with durations.
Progress override invariably produces a shorter critical path and again there could be some illogical lack of dependencies resulting from activities having been progressed out of sequence.
When using critical path methods for analysing delays the contesting parties will often select the opining methods to analyse their schedules – thus producing wildly differing results from what seems like the same base data. As part of their preliminary discussions, I believe that ‘experts’ should agree what method best represents the situation, in my experience neither correctly does. ‘Retained logic’ often needs some dependencies to be delated or their durations modified and ‘progress override’ often needs dependencies to be added to maintain logical sequences.
Whatever method is used a ‘sense check’ is required to ensure the resulting situation accurately models reality (well, as close as we can get at least).
Regards
David
Member for
20 years 10 months
Member for20 years10 months
Submitted by Sooraj G Othayoth on Mon, 2005-11-14 04:20
I would say that it is up to the planner/scheduler which method would be the best to use based on past experience that would allow him/her to forsee the completion of the project(probable completion). By definition, retained logic will reschedule your all remaining activities to follow after its predecessor has been completed... and progress override with ignore the logic and allows activties to be out of sequence...
Using progress override will decrease the number of activities in you critical path (if critical activities have been updated)...
Member for
15 years 8 monthsHi,I wrote an article
Hi,
I wrote an article explaining How does Retained Logic, Progress Override and Actual Dates in Scheduling Options work?
Kindly read it here : https://doduykhuong.wordpress.com/2016/06/08/how-does-retained-logic-progress-override-and-actual-dates-in-scheduling-options-work/
Member for
20 years 10 monthsRE: Retained logic & Progress override
Hello David,
Thank you very much for ur help.
Cheers
sooraj
Member for
23 years 7 monthsRE: Retained logic & Progress override
Hello Sooraj
If a project is generally running according to plan and activities are not progressed out of sequence then there will be virtually no difference between the two methods. BIG differences come when activities are progressed out of sequence.
Most of the time, or at least as a starting point, I believe in retained logic. Invariably that will produce the longest critical path but if activities have been progressed out of sequence, there could be some resulting illogical dependencies remaining, in particular resulting from dependencies with durations.
Progress override invariably produces a shorter critical path and again there could be some illogical lack of dependencies resulting from activities having been progressed out of sequence.
When using critical path methods for analysing delays the contesting parties will often select the opining methods to analyse their schedules – thus producing wildly differing results from what seems like the same base data. As part of their preliminary discussions, I believe that ‘experts’ should agree what method best represents the situation, in my experience neither correctly does. ‘Retained logic’ often needs some dependencies to be delated or their durations modified and ‘progress override’ often needs dependencies to be added to maintain logical sequences.
Whatever method is used a ‘sense check’ is required to ensure the resulting situation accurately models reality (well, as close as we can get at least).
Regards
David
Member for
20 years 10 monthsRE: Retained logic & Progress override
Hello Christian,
Thanks for the reply. That was helpful.
Sooraj
Member for
22 years 5 monthsRE: Retained logic & Progress override
Hello Sooraj,
I would say that it is up to the planner/scheduler which method would be the best to use based on past experience that would allow him/her to forsee the completion of the project(probable completion). By definition, retained logic will reschedule your all remaining activities to follow after its predecessor has been completed... and progress override with ignore the logic and allows activties to be out of sequence...
Using progress override will decrease the number of activities in you critical path (if critical activities have been updated)...
Cheers!
Christian