10.01.2015 Views

Seven secrets of successful PMOs

Seven secrets of successful PMOs

Seven secrets of successful PMOs

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Seven</strong> Secrets <strong>of</strong><br />

Successful <strong>PMOs</strong><br />

Brad Robbins – Solution Q Inc.<br />

brobbins@solutionq.com


Agenda<br />

• Different types <strong>of</strong> <strong>PMOs</strong><br />

• Why is the PMO approach so popular<br />

• Services provided by a PMO<br />

• Common causes for PMO failure<br />

• <strong>Seven</strong> <strong>secrets</strong> <strong>of</strong> <strong>successful</strong> <strong>PMOs</strong><br />

• The rise <strong>of</strong> the virtual PMO<br />

• How Eclipse supports a PMO


Different types <strong>of</strong> <strong>PMOs</strong><br />

• A PMO is…<br />

• An organization entity responsible for oversight over a<br />

portfolio <strong>of</strong> projects<br />

• Variants on a theme<br />

• Portfolio Management Office: Common in organizations<br />

that have adopted PPM practices<br />

• Project Management Office: Common in organizations<br />

that have not yet begun to follow PPM practices – the<br />

portfolio is at best, loosely formed<br />

• Program Management Office: Common in organizations<br />

that are interested in oversight for an interrelated set <strong>of</strong><br />

projects with a shared goal<br />

• Generally the label “Project Management Office” is not a<br />

good indicator <strong>of</strong> what the entity is or does


Why has the PMO approach been<br />

so popular<br />

• To improve project success rates<br />

• To streamline & focus communications<br />

• To improve consistency <strong>of</strong> project planning<br />

& execution<br />

• To support enterprise resource capacity<br />

planning and project portfolio management<br />

• To support a career path for PM-oriented<br />

staff


Why is the PMO approach so<br />

popular (less visible reasons)<br />

• To centralize accountability (with little or no<br />

authority)<br />

• To create an organization entity that can be<br />

blamed when things go wrong on projects<br />

• To create a “watchdog” to keep an eye on<br />

project sponsors & teams<br />

• To provide a convenient place to dump<br />

project managers without establishing a<br />

clear pr<strong>of</strong>essional growth path for them


Services provided by a PMO<br />

• Centralized visibility into project status<br />

• Staff resources to manage projects<br />

• Ongoing support & control for project and<br />

project portfolio management<br />

methodologies<br />

• Provide project management consulting<br />

services to project teams<br />

• Perform delivery assurance checks on<br />

active projects<br />

• Provide decision-support data for project<br />

activities & resource utilization


PMO failure rates<br />

• The PMO approach is a popular method <strong>of</strong><br />

tackling a variety <strong>of</strong> project planning &<br />

delivery issues, however…<br />

• A study <strong>of</strong> 750 organizations worldwide<br />

conducted in 2004-05 * indicated that over<br />

75% <strong>of</strong> organizations that set up a PMO<br />

shut it down within three years because it<br />

did not demonstrate any added value<br />

• PMI did similar research which indicated<br />

that only 17% <strong>of</strong> <strong>PMOs</strong> had been in<br />

existence for more than five years<br />

* Business Improvement Architects


Common causes for PMO failure<br />

• Lack or loss <strong>of</strong> executive sponsorship<br />

• Organization culture not supportive <strong>of</strong> PM<br />

• Lack <strong>of</strong> effective change management during implementation<br />

• Lack <strong>of</strong> involvement <strong>of</strong> key stakeholders<br />

• Lack <strong>of</strong> clear mandate or scope<br />

• Inadequate or ineffective staffing<br />

• Unable to provide tangible evidence that the PMO improves<br />

project success rates<br />

• Increases bureaucracy or administrative overhead without<br />

increasing value<br />

• Creates power struggles within organization<br />

• “Boiling the ocean”


<strong>Seven</strong> <strong>secrets</strong> <strong>of</strong> <strong>successful</strong> <strong>PMOs</strong><br />

1. An actively involved sponsor at the right level <strong>of</strong><br />

authority in the organization effectively supports<br />

the PMO<br />

• If the PMO supports a single department, the C-level<br />

executive for that department should be the sponsor<br />

• If the PMO supports the organization, the PMO should<br />

ideally report to the COO or CEO<br />

2. The PMO fits the organization’s culture and<br />

structure<br />

• Don’t have a “command-and-control” PMO when the<br />

organization culture is consensus or collaboration driven


<strong>Seven</strong> <strong>secrets</strong> <strong>of</strong> <strong>successful</strong> <strong>PMOs</strong><br />

(contd.)<br />

3. The PMO effectively communicates the business<br />

value it has delivered<br />

• The PMO should be created as the approved outcome <strong>of</strong><br />

a business case<br />

• The PMO should log, quantify and communicate all<br />

achievements and acknowledge costs & failures<br />

• The competency <strong>of</strong> the personnel is a key issue in PMO<br />

performance (PMI survey)<br />

4. The scope, services and formal authority for the<br />

PMO are documented & communicated<br />

• This information should be developed as a key<br />

deliverable <strong>of</strong> the PMO initiation project and should be<br />

approved by the PMO’s sponsor


<strong>Seven</strong> <strong>secrets</strong> <strong>of</strong> <strong>successful</strong> <strong>PMOs</strong><br />

(contd.)<br />

5. Changes are rolled out incrementally using proper<br />

organization change management practices<br />

• Work with HR to define the appropriate communication<br />

messages & training for process and procedure changes<br />

6. The PMO implementation is managed as a project<br />

• Assign a PM, develop a charter, involve stakeholders, manage<br />

risks, develop and track to a budget & schedule, etc.<br />

7. The PMO is supported by technology that reduces<br />

administration effort & increases the likelihood <strong>of</strong> process<br />

compliance<br />

• Technology without process will automate chaos, but process<br />

without effective supporting technology creates administrative<br />

overhead<br />

• Most <strong>PMOs</strong> have a very small staff as these staff are <strong>of</strong>ten<br />

regarded as overhead (PMI survey)


The rise <strong>of</strong> the virtual PMO<br />

• Problem: Establishing a new organization<br />

entity might be “too much change” for<br />

some companies<br />

• A popular solution: Virtual PMO<br />

• Delivery <strong>of</strong> PM services is distributed across<br />

different organizational units or staff<br />

• Needs an actively involved sponsor at the right<br />

level <strong>of</strong> authority<br />

• Requires technology to facilitate consistency,<br />

compliance & communications


How Eclipse supports a PMO:<br />

Overall project status


How Eclipse supports a PMO:<br />

Schedule status


How Eclipse supports a PMO:<br />

Resource capacity planning


How Eclipse supports a PMO:<br />

Consistency & Reuse


Questions<br />

brobbins@solutionq.com

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!