One thing I would add to the list is: relative lack of evidence. Now don't get me wrong, unit testing, continuous refactoring and pair programming are very help

One thing I would add to the list is: relative lack of evidence. Now don't get me wrong, unit testing, continuous refactoring and pair programming are very helpful when applied in the right context. But there is a lot of code out there that was written with no overt agile enthusiasm, and this code is working just fine. I always roll my eyes when I hear or read things like: "if you don't write your tests first you're doing it wrong". I'm very happy that TDD and daily scrums work for you, but I won't convert to your religion unless you show me a search engine or a web browser written with agile consultants on site.