Dears,
I know I should avoid mandatory constraints, but the client forces the team to use a mandatory finish milestone (Project Finish Date) that leads to negative lag. Our mandatory finish constraint on “Project Finish Date” caused a network logic violation, where the successor completes before the predecessor.
I want to know if there is any way that all preceding activities fall into line before the “Project Finish Date”?
Thanks
Hi:
mandatory constraints (for start/finish dates) are usable for an initial reference, but should be avoided in the schedule.
If you get negative float (or force the use of negative lags), it is an indication that the total time (for a mandatory finish date) is no enough.
As mentioned by other colleague, is up to the Manager or Project board to decide how to solve -by example by schedule compression-, considering that the risk to achieve planned finish date is increased.
regards
Hello Hamid,
While dealing with client-mandated constraints like a mandatory finish date with negative lag can be challenging, proactive communication, negotiation for realistic constraints, and careful schedule management are key to ensuring that all preceding activities align appropriately with the project's goals and timelines.
Thanks,
The negative float is the problem your management has to solve. The early dates are what you are planning to do based on the current schedule. The late dates are what you are required to do to achieve the contract completion. The difference (negative float) is the challenge.
Accellerating the schedule in the computer is quite easy - doing it in the field is a lot harder. For more on schedule compression see the WP Schedule Compression at: https://mosaicprojects.com.au/PMKI-SCH-014.php#Process6
Thanks David
Indeed there is, Hamid.
The late dates show what you are looking for.
Yes, you should not use mandatory dates.