Agile development pitfalls
A methodology is a good thing, isn't it? Sure, nothing can replace experienced programmers, and a porject is doomed at start if taken in the wrong technical direction. So, any given methodology can work for some, and not work for many.
The number one problem with the big "M" Methodology is that it relies on "paperwork" replacing people skills, it takes the responsability from the individual and gives it to the "institution", often rendering an semi-automated process that can produce lots of documentation on how to develop a low quality product.
Beeing not a friend of paperwork, I have been looking into Agile methodologies.
Here is a good article that looks into some common pitfalls of implementing such types of methodologies.