The same train of thought leads to the idea that you can produce good software with mediocre developers by using processes, coding rules and checklists and "development methodology" like agile.
But to most, it is just putting lipstick on the same old pig.
Did I mention the whole training, coaches and lango flinging industry?
Fundamentally, dev is something to negotiate with, cooperatively, versus commanding "do what I say"-style. Many businesses are unable or unwilling to do away with this top-down hierarchy, hence agile will never succeed there.
The agile they practise instead is "Agile, but without actually relinquishing top-down control".
TBH, I think what we are really missing is for the development team to be a contract team (ala Accenture) that can implement agile via official mediums e.g. pushback via contractually negotiation, backlog prioritisation via contract pricing ("we can do that, but this is what it'll cost").
We do have very capable drag and drop CRUD generators now (not quite the same, but I still have a soft spot for VB5). But, what's expected, even out of a simple CRUD form, has risen.
I'm reminded of that today in the rare instance when I run into the decision makers that are convinced GUI data engineering tools are the future.