It does seem that missing milestones is an unfortunate part of the project process. Sure, as aforementioned, missing milestones can lead to overall improvement of the product. That is, if the missed milestone was unforeseen or having to do with the research and development of the product. However, if the milestone was due to negligence or carelessness in the process, then this milestone is not a good thing. One can argue that this missed milestone due to negligence can alert the engineers in order to improve their process. However, in the grand scheme of how the company is operating, this missed milestone cannot be framed as a good one. Any hiccup in the process can be viewed at as negatively or positively, and can greatly affect the overall mood of the engineering team. After a milestone is missed, the project manager and team need to address the cause of missing the milestone and whether or not it could have been avoided. There are some times when the responsibility is out of the team's hands. However, for when it's not, the team needs to analyze and improve their abilities, and not focus on whether or not missing the milestone is good or bad.