WaffleMonster is clearly too young to have lived through the waterfall era, or wouldn't say such silly things.
WF was terrible. And most people doing it would admit, with some guilt, that they weren't doing it according to "serious" WF principles.
Scrum is not the problem. The problem is bad managers that don't understand software development. Maybe going back to an oldie such as "Debugging the Software Development Process" by Steve MacGuire can give some insights on how to do it right. And then you do it right, and along the way when people ask you what you're doing, just say "Scrum" and all will be fine.
But not understanding how to do software development is not compensated by any methodology. What people need to understand (and the book by Steve McConnell, "Rapid Application Development' illustrates well) is that a Software Engineering manager has a set of tools in his or her toolbox. And can choose what tools to use. These include, daily scrums, unit tests, UI designs, code reviews, etc.. etc.. The correct mix is achieved according to what team you have. It has to be dictated by the capacity of the team, and the conditions of the project.
Also, businesses typically want estimates. So read McConnell's "Software Estimation: Demystifying the Black Art" so you can learn how to handle that business need as well.
Running a software project requires more know how, that a single Scrum or Agile course. But Scrum and Agile tools can be very useful in real world projects.