Agile methodology was the solution to the problem of Waterfall methodology. I am tending to see this pattern in many articles. Those who never got "burned" by limitations of traditional DB's and lists the problems of NoSQL. I worked in Siemens telecomm initially where most of the SW running in the telecom switches and management was in hardcore waterfall. And it was a huge success; and pretty good quality. But at what cost ! God every team is supposed to Analyse and Estimate and everyone added comfortable buffers. I did TDD then; many good programmers also did. Such things have nothing to do with Agile or Waterfall. When the first Agile consultants came to us, as the company was bleeding due to the huge overheads, and once a decade releases; it was like water to a traveler in the desert. I first heard things like CI/CD there. Does Agile have its problems, is like asking which solution does not have its own problems. It is foolish to practice one thing or the other, but practice many. "Agile is an anti-process and hence it cannot fail, nor succeed. You can be agile, you cannot do agile. " https://medium.com/better-software/sw-engineering-101-c711e948b065