It&#x27;s not though. This is why Agile is such a failure. Because people don&#x27;t actually read the Manifesto.<p>It doesn&#x27;t say planning is unimportant. It doesn&#x27;t say contract negotiation is unimportant. It doesn&#x27;t say timelines and knowing what you&#x27;re doing is unimportant.<p>You can and should do all these things. It&#x27;s amazing to me that Software Developers seem to believe their job is somehow unique and it&#x27;s just not possible to do simple things General Contractors and real Engineers do every day.<p>Agile is just a set of values that amount to &quot;be pragmatic and flexible&quot;.<p>You can totally do that without Scrum and avoiding any sort of planning until the last possible moment.<p>IME actual requirements almost never change in software. They&#x27;re just frequently not surfaced until code hits the page because little to no due diligence was done on them. And I very very rarely see a case where an issue with fulfilling the client&#x27;s desires as given couldn&#x27;t have been surfaced and resolved very early on if someone had just sat down and thought about it for a few minutes before going off and promising something that couldn&#x27;t be delivered in the time or budget allowed.