Missing a milestone can stem for several reasons. It is important to point that out. However, in general, I believe that missing a milestone is not beneficial for the project. This is because a lot of the further stages of the project depend on the completion of the previous components of the project. This causes problems because this prevents the furtherance of the project into the next stage. If there is an unforeseen problem that comes up which prevents the project from continuing, it is important that this type of setback be factored in when making of the initial schedule. When the PM creates the schedule, it is in the best interest to come up with a schedule that factors in a thorough development of the assigned stage. Missing a milestone not only uses up time but also cost. Every aspect of the project costs money and extending/prolonging it increases the cost. In order to prevent recalls and ensuring the product is safe and works as expected, another group within the project is assigned to do that and does the assessment concurrently as the development in order to save time.