This starts with a false statement--"The “Agile” fad grew up in web consulting"--and just continues downhill. I'm going to try and not make this criticism a No

This starts with a false statement--"The “Agile” fad grew up in web consulting"--and just continues downhill. I'm going to try and not make this criticism a No True Scotsman, but this post describes a vaguely Scrum-flavored approach that explicitly violates many of its stated intents. If the purpose of this post was to decry cargo-cult agile where the trappings and software of Scrum or Kanban are adopted without paying heed to the intent, I'd be wholeheartedly agreeing. But it seems the author has conflated the two. If information is flowing only one way, from product owners to engineers, whose only upstream delivery is their reporting, you're not looking at agile but at some weird sprint-chunked waterfall process.