Agile only seems to be useful if you have prior exposure to the Waterfall model, people who start off with Agile as their first software development methodology

Agile only seems to be useful if you have prior exposure to the Waterfall model, people who start off with Agile as their first software development methodology tend to parse 'agile' as 'license to freely use bad practices'. I've seen this often enough to a point, at times I think the older waterfall model would work a lot better for a lot of shops. Back in the day people would do a good deal of paper work as a part of requirements gathering, this would iron out a lot of clarification and specify clear definitions of what people wanted to do. These days 'define as you code', often leads to getting requirements in piece meal, often adhoc with no broader sense of design and what follows is endless refactoring. Delayed projects, and rewrites. One more damage agile is causing to the Google generation of programmers is destroying skills related to reading and writing documentation. In a urge to do everything in a hurry, we end up doing more damage than good. And agile never quite really got rid of beaucracratic rituals of the waterfall model, they just got re invented into their new forms.