This is not entirely a bad thing, although many of the negative conclusions drawn by the author are true. One of main obstacles for going Agile has always been

This is not entirely a bad thing, although many of the negative conclusions drawn by the author are true. One of main obstacles for going Agile has always been that it really needed all of the organisation to change, not just the developers. Also, Agile conferences aren't really that interesting for developers anymore. We've already adopted most of the development practices to the point where many developers are no longer aware that they came out of, or at least became mainstream because of, the Agile and XP movement. Most of us are Agile without being aware of it, which in turn leads to hilarious anti-Agile rants (based on experiences with top-down enforced cargo cult "Agile") in which the authors propose alternative practices that are typically Agile and tick all the boxes of the Agile manifesto... The hard part about Agile is still adapting the entire organisation's processes, which generally is of more interest to management-types than to developers. Finally, you would be surprised to learn how many people that are active stakeholders in software development processes only now start to learn what Agile is. For most of us, in our fashions and fads driven bubble end of the industry, Agile is already passé, but for many it's still a revelation.