This is the "mid-term project verification line

[hasan018542]

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.

At least don't wait until the last minute to belgium mobile database realize that you can't finish it, because at this time there is often no room for communication and maneuver.

So what about the third deadline: "sprint results in the short term"? This is to ensure that the next mid-term project milestone I set can be completed relatively on schedule , so I will use one or two weeks as the interval to set the (intermediate) key results of the project that I can produce quickly during this period.