Thanks guys ... yes you right it's cheatting we all know that but just at the current time to keep our contract and project ongoing and the owner happy without threating to close the project. the best thing to do is by working double shifts so we can reduce the -ve TF and back to the track. Thanks again guys...
That is what I call cheating! If you are culpable for the delay then the best way to do it is to study the programme's critical path where you have negative float and plan a real delay recovery measure(s) (DRM) by increasing resources, or by working double shifts and study where you can pull back some time, once a project is delayed, it is very diffcult to recover.
If the other party is culpable for the delay, then it is in your advantage to show the real delay and ask for extension of time.
Thanks guys ... yes you right
Thanks guys ... yes you right it's cheatting we all know that but just at the current time to keep our contract and project ongoing and the owner happy without threating to close the project. the best thing to do is by working double shifts so we can reduce the -ve TF and back to the track. Thanks again guys...
Hi Hanson Take off all the
Hi Hanson
Take off all the constraints and see what your true delay position is.
Then follow Daniels advice.
Best regards
Mike Testro
Hanson,That is what I call
Hanson,
That is what I call cheating! If you are culpable for the delay then the best way to do it is to study the programme's critical path where you have negative float and plan a real delay recovery measure(s) (DRM) by increasing resources, or by working double shifts and study where you can pull back some time, once a project is delayed, it is very diffcult to recover.
If the other party is culpable for the delay, then it is in your advantage to show the real delay and ask for extension of time.
Best regards,
Daniel
Hanson, Filter to critical
Hanson,
Filter to critical path and reduce some lags accordingly.