It must be considered that there is nothing more difficult to carry out nor more doubtful of success nor more dangerous to handle than to initiate a new order of things – Machiavelli 1446-1507, Italian statesman and philosopher
The problem with the definition of the “Strong” or “Directive” definition above is that in many cases, especially in larger organizations, PMO utilizes personnel provided to them by the functional organizations through a matrix. Therefore they do not assign resources. (While they should and do have an input on that).
Additionally the definition does not mention that PMO holds all of the budgets and is primarily responsible for all project execution and that the functional groups support them.
Lastly they represent or actually are the “customer”. If there is no outside customer they become the internal customer representing the interests of the whole company or if there is an outside customer they become their internal representative.
As I am sure you can see there is a world of difference between the all too common “Weak” models (Supporting and Controlling) and the Strong Model (Directive). And that has primarily to do with responsibility and authority.
To stress these differences and provide my reasons for the Strong model being greatly preferred I will list the specific differences.
Before I do that I would like to make one more observation.
I have worked in and with many industries and companies. I have discussed best practice adoption with Gartner. I have conversed with many others across a broad array of industries.
There is one other glaring and almost black and white difference between the Strong and Weak models. Best practice use. In almost every case, commercial IT being the best example, very, very few of the PM best practices are used in organizations that have the Weak PMO model.
The opposite is obviously prevalent for the Strong model.
I do not think this is by accident. I think this happens because companies that use Weak PMO organizations allow functional managers to be in charge or budgets, people and practices. (Whether a Weak PMO suggests them or not).
This creates a massive conflict of interest.
Functional managers rarely create processes that would wind up holding themselves more objectively and measurably accountable. These missing processes include: EVM, PBS, WBS, schedules with dependencies and critical paths shown, Productivity and Quality Metrics. (And before anyone thinks about responding with the suggestion these things do not apply. They always do. Regardless of what industry you are in. Especially for those creating software. But they have to be used properly. Most often you will find those who say these do not apply have never used them correctly and/or are using scare tactics to avoid that objective and measurable accountability I mentioned. And yes they work for Agile).
Devolves PMs down to Coordinators at best in many situations.
There is no such thing as a perfect process set or organizational structure. But there is what works best most often.
Some degree of poor practice use can be overcome by great teams (which are rare as well. Even though we like to think otherwise) and great practices can be wiped out by bad leadership.
But Apples to Apples I believe the Strong PMO structure is far better than the Weak model.
The primary reason there is inherently less politics and as such inherently less selfishness, stonewalling, delay and settling in order to further individual leader’s personnel interests.
Lessening those politics and counterproductive levels of “democracy” results in better and faster decisions in the company’s best interest.
This structure also usually leads to use of actual best practices which in many cases is even more important than the Strong PMO model being in place. I believe this occurs because the PMO is acting as the company/customer. As such imposing objective measures on those who support them is always easier than leaders doing so to themselves. (As for the Strong PMO having to much power and being held accountable themselves. Those functional managers should have C-Level representation as well as the Strong PMO. They should have say in how affective the PMO and their practices are. Additionally all of those objective measures I have been talking about also reflect on the PMs ability to do their jobs as well. They own cost and schedule. The functional groups own the people and processes that create the product.)
Pingback: What Is a Strong PMO? - PMO Journal()
Finding suitable resources for a large portfolio of projects - via @SaverioLosito #pmot bit.ly/2oZJJQ6
Types of PMO and the journey of maturity - via @SaverioLosito #pmot bit.ly/Jn65Cf
IT Helpdesk Managers: 7 Must-Have Skills, and the 1 Skill You Never Knew About - via @SaverioLosito #pmot bit.ly/1HA8ib1
How to effectively manage the quality of projects without an independent QA department - via... bit.ly/2lAf2zJ
Stay out of the weeds - via @SaverioLosito #pmot bit.ly/Un2tAx
Lessons Learned – The effective Project Management - via @SaverioLosito #pmot bit.ly/157yfee
Con questo codice promo riceverai su mytaxi 20 € per la tua prima corsa che pagherai tramite App: saverio.los - mytaxi.com
The art of Delegation: How to do it Effectively - via @SaverioLosito #pmot bit.ly/2nslyc6
Measuring the Profitability of your Projects - via @SaverioLosito #pmot bit.ly/1TH8gxW
Agile Estimating Tool - Planning Poker using Fibonacci Sequence - via @SaverioLosito #pmot bit.ly/1kRC3Hv
The latest The Program Manager's Paper! paper.li/SaverioLosi… #pmot #projectmanagement
The “recipe” for success in major projects! - via @SaverioLosito #pmot bit.ly/1n9rMqP
Il 49% delle aziende teme problemi di #security e violazione #privacy dai propri dipendenti - fonte @Clusit @polimi pic.twitter.com/n8Al…
How To Give Highly Effective Feedback At Work - via @SaverioLosito #pmot bit.ly/1VWZW0M
4 Mistakes Virtual Managers Make That Stress Out Project Team - via @SaverioLosito #pmot bit.ly/1gHm74r
Top 5 Tips For a Successful Project Manager - via @SaverioLosito #pmot bit.ly/19fdWHQ
The Contribution of a Project Manager to Enterprise Risk Management - via @SaverioLosito #pmot bit.ly/1BseYyr
Future of Work - How It Could Impact You as a Program Manager? - via @SaverioLosito #pmot bit.ly/1D56zGn
Dai un'occhiata a questo Vino. Gli do 3 su 5 stelle con il @vivino app: vivino.com/users/sav…
Profumatissimo, fresco, una bol... Vino da @PellegrinoWine tramite @vivino app: vivino.com/users/sav…
5 Lessons hiding in every Project Management Strategy - via @SaverioLosito #pmot bit.ly/UaEJEI
The PMO - What's the right level of Authority? - via @SaverioLosito #pmot bit.ly/1hboGjf
APMG Change Management approach as a Project Manager - via @SaverioLosito #pmot bit.ly/1MGvMM0
How to create value as a Leader - via @SaverioLosito #pmot bit.ly/2rDwn9J
Using Harvey Balls to Convey Qualitative Information - via @SaverioLosito #pmot bit.ly/2fktjwN
Benefits Management - a Program Management Fundamental - via @SaverioLosito #pmot bit.ly/1yhVfmP
Don't Expect Project Management Teamwork, Lead It! - via @SaverioLosito #pmot bit.ly/1K5yAhT
View my verified achievement from Project Management Institute on Acclaim. youracclaim.com/badg…
Project management survival skills toolkit - via @SaverioLosito #pmot bit.ly/2p5zhnX
6 Project Management Trends To Look Forward In 2017 - via @SaverioLosito #pmot bit.ly/2kUiymR
Help the growth of this blog