Even with Agile and Scrum waterfall will sneak in
I&#x27;ve never quite understood, over 30 years of experience in software development, what problems Waterfall presented that warranted a complete refactor of software development processes such that things are now very much in cult-&#x2F;cargo-cult  territory.<p>There is a natural process that every issue goes through: Analysis, Specifications, Requirement, Design .. then the Developer takes in the materials of each of these steps, does an Implementation and Testing phase .. then the issue has to be validated&#x2F;verified with a Qualification step, and then it gets released to the end user&#x2F;product owner, who sign off on it.<p>This is a natural flow of steps, and it always appears to me that the new-fangled developer cults are always trying to &#x27;prove&#x27; that these aren&#x27;t natural steps, by either cramming every step into one phase (we only do &quot;Analysis&quot; and call it Scrum) or by throwing away steps (Qualification?  What&#x27;s that?) and then wondering why things are crap.<p>Too many times, projects I&#x27;ve seen fail could&#x27;ve been saved if they&#x27;d just gotten rid of the cult-think.<p>Its nice, therefore, to see someone else making the observation that Waterfall is a natural process and all the other -isms are just sugar&#x2F;crap-coating what is a natural consequence of organizing computing around the OSI model - something that has been effective for decades now, and doesn&#x27;t need improvement-from-the-youth antics.