The book AntiPatterns in Project Management cried out this morning to be thumbed through again. I had written a review when the book was first published and hadn't really looked through it until today.
What struck me is how obvious the antipatterns fit the discussion of agile project management. Maybe if the discussion of APM started with - "I'm referencing antipattern number XYZ when I'm recommending a specific APM process..." much of the confusion over "what is APM" would disappear.
If you don't own the book, buy it. If you haven't read it, read it. If you haven't thumbed thorugh it in some time, do so...much of the discussion around APM should be built on antipatterns
