You will find that the M&C is highly correlated to the a properly defined scope. Many of you have mentioned capstone, and I am sure that as you began actually building the product you realized that your understanding of the scope of the project or the time scale for each component based off your understanding of that component from the scope determined if you were in the positive or negative because the scope is what eventually leads to the definition of the predicted/expected budget and time. One of the components that resulted in a major set back for was the compatibility of components and the idea that a component that was delivered could be defective. We had spent a whole weeks trying to transmit information from an arduino through wifi to a remote server but found out that the wifi chip was defective and after purchasing a new chip, the initial code worked fine. This was a rate determining step in our gant chart and it resulted in delays. With a perfectly designed scope, you would be able to have a neutral net being just on time similar to how if you had to do the capstone project again you would be able to quite accurately define the time needed to finish ever step as well as have every step needed well defined.