&gt; In other words, projects are late because business justification is usually weak for software projects.<p>While that&#x27;s sometimes true, I read exactly the opposite. I read what he said as: 1- Software projects don&#x27;t start until justification is strong, and 2- justification doesn&#x27;t become strong until it&#x27;s already too late.<p>So, the problem isn&#x27;t (necessarily) that justification is weak, it&#x27;s that strong justification is itself a red flag, because it&#x27;s already too late to start if you have a really good business case for it, you should have started before you had all the data to prove you needed to start.<p>But, I don&#x27;t think he&#x27;s necessarily saying we should be able to somehow predict the future and start software projects before we know for sure we need them, he&#x27;s just reflecting on patterns observed and providing more of a thought framework for dealing with these patterns.