10 Ways to Destroy the Effectiveness of Your Project Management Office (PMO)

by Alec Satin

Destroy your team

For every PMO that delivers on its initial promise, there are two that hobble along, never really achieving much in terms of bottom-line benefit to customers, project managers, stakeholders or the business itself.

It’s pretty easy to eliminate most if not all  benefits of a Project Management Office.  Which of the following hold true for your PMO?

  1. Make sure to set up a climate of fear. Emphasize the penalties of non-compliance.  Use the stick and not the carrot.
  2. Make sure to locate the program office as far away from the project managers as possible. Extra points if you make communication hard by limiting the use of online collaboration software and other tools.
  3. Do not include project managers in decision-making. Take a heavy handed approach.  Issue pronouncements whenever you come up with a novel way of doing things.
  4. Metrics over people. Make sure that the project managers understand that success means not more than 10% schedule and cost variance.  Qualitative measures should never enter into any equation.  Come to think of it, what are qualitative measures?  Don’t bother me with irrelevancies.
  5. Leave vision to Oprah and Deepak. This is IT.  We’re here to deliver.  PMs should focus on getting the work done.  They don’t need to know about business goals, objectives, and customer needs.  Just read the documentation and get to work.
  6. Discourage and eliminate contact between project managers. Make sure that all communication is rigidly defined, regimented and as unpleasant as possible.  Set meetings at inopportune times and force people to attend who have little to offer or gain by being there.
  7. Do not define standard processes and templates. If you have processes, provide them only when absolutely necessary.  Do not give training.  If you must provide training, allow only a small fraction of your personnel to attend.  Do not include any contractor staff in training.
  8. Establish your PMO as an entity unto itself. Provide minimal alignment up to higher management or down to the needs of the project managers.
  9. Focus on irrelevancies.
  10. Implement ITIL, SDLC, EVM, Project Server or any toolset without first establishing a firm foundation of project management best practices throughout your organization.

There you have it.  Ten steps to ensure that all your efforts will end in mediocrity.  Coming soon – the ten steps to ensure that your PMO will be a bright light to lead your organization to great project management success.

As always, wish you well.
Alec
(Image by trueblood on flickr)

If you liked this article, please Tweet it! twitter bird image or Bookmark it  delicious image

{ 5 trackbacks }

Is your IT Team’s Culture Aligned with the Business? | Strategic IT Planning Blog
13 December 2008 at 4:16 pm
7 Marks of a Best PMO | Strategic IT Planning Blog
27 January 2009 at 6:13 am
Leadership Skills for IT Managers - 10 Things Learned at Grid International Training
12 March 2009 at 3:37 pm
7 Marks of a Great Project Management Office
31 August 2009 at 8:59 am
Steven Peltzman
27 October 2009 at 1:40 pm

{ 6 comments… read them below or add one }

1 Andres 7 August 2008 at 12:03 pm

Very good points. I liked the post. Digg’d and Stumble’d.

Reply

2 PM Hut 3 October 2008 at 2:28 pm

This is an excellent article. I do have a distantly similar musing about the PMO: the PMO Poem.

About #6: “Discourage and eliminate contact with and between project managers.” I think a lot of people can relate even more to it when it’s “Discourage and eliminate contact between project managers.”

PM Hut´s last blog post..Is a Career in Project Management Right for You?

Reply

3 Alec Satin 5 October 2008 at 2:54 pm

Twitter: alecsatin
Hi PM Hut,

Your PMO Poem captures so much of what happens with PMO implementation. I loved it!

Appreciate your comment, and have updated the post as recommended.
Alec

Alec Satin´s last blog post..How to Say Goodbye When a Workmate Leaves

Reply

4 Derek Huether 23 March 2009 at 8:26 am

Twitter: derekhuether
Alec,
I’ve been in an environment where your list of how to eliminate most if not all benefits of a PMO read like commandments. In retrospect, a little inspiration and empowerment would have gone a long way. Thank you for helping us keep some perspective.

Regards,
Derek Huether, PMP

Derek Huether´s last blog post..Understanding Agile Scrum and common terms

Reply

5 Alec Satin 23 March 2009 at 8:42 am

Twitter: alecsatin
Hi Derek,
So sorry to hear of your experience – which may be more common than not in PMOs. Perhaps this is the reason that a recent poll found that most executives did not believe that their organizations were getting the possible benefits from their PMOs. Inspiration and empowerment does go a long way to encourage those doing the actual work. Ultimately these iron-fist PMOs will be reformed willingly or through pressure from above. Think dinosaur.
On a happier note, enjoyed your Agile and Lessons Learned Posts, and have subscribed to your blog.
Look forward to future conversation here or there.
Alec

Reply

6 Derek Huether 23 March 2009 at 10:35 am

Twitter: derekhuether
Alec,
Just an update. The economy caught up to my last experience and I found myself without a job. I should have known there was trouble when I sat across the table from my boss and asked specifically what type of PMO the business expected us to be. (General, Supportive, Controlling, or Directive). My question was met with an uncomfortable silence, followed by “type?
My new experience is a better one and I look forward to writing about it.

Thank you Technorati for leading me to your blog!
Derek

Derek Huether´s last blog post..Understanding Agile Scrum and common terms

Reply

Leave a Comment

You can use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

CommentLuv Enabled

Previous post:

Next post: