The document discusses the need for transparency when a project's scope changes due to circumstances like weather or incompetence. It notes that stakeholders must be informed of the truth and solutions found. If incompetence caused issues, those responsible should be confronted and corrective measures taken, possibly even termination. The document also cautions that scope creep without a formal process can lead to problems, giving an example from a past software project where establishing rules helped get things under control.