Software Methodology: Why One Size Fits No One
Regardless of intent or documentation, I’ve never come across a methodology that didn’t devolve into the same practice as every other methodology.  The root problem is that the people who are looking for a methodology/silver bullet are convinced — and no amount of reality will ever convince them otherwise — that software development can be done with 100% predictability, just like, say, adding a garage to a house.  So even XP, that explicitly states up front that this is not possible in software, gets morphed into “agile” which is actually a great way to manage predictable development tasks, but a horrible way to manage software.