>Agile as per the Agile Manifesto isn't bad. At all.
If you actually read it it really is just a bunch of words that doesn't specify much of anything at all. To me it reads as something incredibly vague and hand-wavy and how on earth modern Agile has been inferred out of the text of the agile manifesto is somewhat beyond me.
It's a product of its time, it has seeded practices that for us is common knowledge nowadays. In 2005 it wasn't, most software companies were still stuck with long feedback loops, hierarchical decision making and goal-setting, over-analysis of requirements and little to no maneuvering room to change requirements once development was started.
It's vague exactly because it's a manifesto, not a handbook on how to apply it.
If you actually read it it really is just a bunch of words that doesn't specify much of anything at all. To me it reads as something incredibly vague and hand-wavy and how on earth modern Agile has been inferred out of the text of the agile manifesto is somewhat beyond me.