Which PM “faux pas” make your hair stand on end?

In my last post about the “school solution,” I noted that there’s something unnerving about project and program managers who skip over the basics.  As Glen Alleman noted in his comment, the PM school solution or black letter law almost always has some merit as a start.

Thinking about this post brought to mind the various project management myths, missteps, and mistakes that put me on edge.  These three always make me wonder about the person who says them:

  • Calling a project schedule a project plan.
  • Not knowing the difference between an issue and a risk.
  • Suggesting that planning is useless if we don’t know all of the activities.

What are your pet peeves?  Which PM faux pas makes you nervous, irritable, and discontented with those who make them?

I smell a poll here!

Don’t over-interpret the PMBOK Guide…

I just got turned on to Glen Alleman’s Herding Cats blog via Bas’s Shared Blog.  Bas’s link was to one post, but Glen’s post on Mis-Misinterpretations of PMBOK caught my eye (the comments are a good read also).  Glen hits on one of my favorite mis-steps: claiming a methodology isn’t PMBOK-compliant because it isn’t structured according the process groups (hint: the project life cycle discussion is in Chapter 2 of the Third Edition). 

Getting caught up in memorizing and regurgitating such industry standards is a pet peeve.  It is akin to being an expert on Black Letter Law: how interesting or useful is it to be an expert on something basic and elementary?

%d bloggers like this: