Let me give you a smaller example. Once I received a request from a foreign

[hasan018542]

I received a request from a foreign customer, hoping to receive a product we were producing in two months. So the first relatively simple deadline appeared, which is that overseas customers must receive the product two months later. This is the "final deadline."

But before I explicitly agreed to this deadline, I first did a "phased results breakdown" of the project . I needed to advance several progress to complete the above deadline. If we work backwards from the final deadline, it includes:

How long is the delivery date needed to send the product to overseas customers?
How much time does it take from the belgium mobile database completion of product production to picking and packaging?
How much time is left to complete the product?
So I might set up several mid-term project verification lines (milestones) like this:

Finally, two weeks were left to deal with the product delivery.
One week is left in between to handle product picking and packaging.
I have a little over a month from now to finish the product.
This is the "mid-term project verification line". The benefit of setting this mid-term milestone is that we can have a more specific understanding of the risks before the deadline, because it is really "difficult" to advance the project completely as planned, but at least we need to control ourselves : If I find at any time that I cannot complete the product in a month, then I should quickly research alternative solutions to complete the product on time, or research whether there is a faster packaging process, or ask if there is a faster way of shipping, or even communicate with the customer whether the date can be rescheduled.