Chanukya RajagopalaDirector - IT Strategy - R & D| iPOCA Private LtdUnited Kingdom
Can there be more than one PMO in a business?
Consider the organisation to be large......
Programmes/Portfolios are diverse and varied, (however overall business objectives are common)...
Resources are common for both PMOs, if set up.
Industry - Large IT company, with 100s of projects, under different programmes
Will it work?
Potential Problems?
Please share your thoughts if 2 PMOs in a business is a viable proposition? Saving Changes...
Sort By:
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
First of all, a company could have more than one business defined into it. So, you can have more than one PMO in the same company if you distribute it between its business. Second, you can have more than one PMO for example taking into account the enteprise architecture (business, application, technology, secutiry, information layers) but you have to define one EPMO (enteprise PMO) that will integrate the others. I am working inside a company with multimple PMOs.
...
1 reply by Chanukya Rajagopala
Jan 02, 2017 3:27 AM
Chanukya Rajagopala
...
Thank you Sergio,
Your comment of one EPMO and ther PMos integrating into it, makes the entire set up map crystal clear to me. I can already see the benefits and issues.
Great reply Sergio. thanks again.
Saving Changes...
saurabh mahajanPMP, ITIL, PRINCE2| vodafonePune, Maharashtra, India
Yes multiple PMO's is feasible. And as mentioned by Sergio based on enterprise architecture and verticals.
...
1 reply by Chanukya Rajagopala
Jan 02, 2017 3:28 AM
Chanukya Rajagopala
...
Thanks for the reply Saurabh. Your reply reaffirms Sergio's advice.
Saving Changes...
Sean WhitakerProject Management Consultant| Crystal ConsultingChristchurch, New Zealand
The structure, type and number of PMO's in any organisation should always match its current level of organisational project management maturity and its aspirations over the next 2-3 years. If it decides that more than one is appropriate then it should ensure there is clear demarcation and definition of responsibility and accountability. There should also be a focus on avoiding unnecessary duplication.
...
1 reply by Chanukya Rajagopala
Jan 02, 2017 3:31 AM
Chanukya Rajagopala
...
Sean, thanks for your advisory. Your logical approach into the feasibility assessment for additional PMOs gives me the necessary guidance to alter my maturity plan to drive the need and setup on the second PMO.
Thank you.
Saving Changes...
Chanukya RajagopalaDirector - IT Strategy - R & D| iPOCA Private LtdUnited Kingdom
Jan 01, 2017 6:15 PM
Replying to Sergio Luis Conte
...
First of all, a company could have more than one business defined into it. So, you can have more than one PMO in the same company if you distribute it between its business. Second, you can have more than one PMO for example taking into account the enteprise architecture (business, application, technology, secutiry, information layers) but you have to define one EPMO (enteprise PMO) that will integrate the others. I am working inside a company with multimple PMOs.
Thank you Sergio,
Your comment of one EPMO and ther PMos integrating into it, makes the entire set up map crystal clear to me. I can already see the benefits and issues.
Great reply Sergio. thanks again.
...
1 reply by Sergio Luis Conte
Jan 02, 2017 5:09 AM
Sergio Luis Conte
...
You are welcome. I hope it helps you. Regards
Saving Changes...
Chanukya RajagopalaDirector - IT Strategy - R & D| iPOCA Private LtdUnited Kingdom
Jan 02, 2017 1:34 AM
Replying to saurabh mahajan
...
Yes multiple PMO's is feasible. And as mentioned by Sergio based on enterprise architecture and verticals.
Thanks for the reply Saurabh. Your reply reaffirms Sergio's advice. Saving Changes...
Chanukya RajagopalaDirector - IT Strategy - R & D| iPOCA Private LtdUnited Kingdom
Jan 02, 2017 1:43 AM
Replying to Sean Whitaker
...
The structure, type and number of PMO's in any organisation should always match its current level of organisational project management maturity and its aspirations over the next 2-3 years. If it decides that more than one is appropriate then it should ensure there is clear demarcation and definition of responsibility and accountability. There should also be a focus on avoiding unnecessary duplication.
Sean, thanks for your advisory. Your logical approach into the feasibility assessment for additional PMOs gives me the necessary guidance to alter my maturity plan to drive the need and setup on the second PMO.
Thank you. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Jan 02, 2017 3:27 AM
Replying to Chanukya Rajagopala
...
Thank you Sergio,
Your comment of one EPMO and ther PMos integrating into it, makes the entire set up map crystal clear to me. I can already see the benefits and issues.
Great reply Sergio. thanks again.
You are welcome. I hope it helps you. Regards Saving Changes...
Wagner MeanaProject Manager| Istmo Tecnologia / ClaroSão Paulo, São Paulo, Brazil
The main point is the division of activities between each team member, no matter if they are PMOs or Project Managers. Saving Changes...
Drew CraigSr. Agile & Product Coach| VanguardPhiladelphia, Pa, United States
We have PMO's per verticals. Ideally, this scenario would have an EPMO. Enterprise Architecture and VMO should be strategically aligned with each PMO and the EPMO. Saving Changes...
