Ganesh KumarProgram ManagerBangalore., Karnataka, India
Dear Team,
What are the “quantifiable” achievements of project/program management office. When we discussed internally, “Change Request” came up as a point, whenever there is any change, resulting in commercial value.
What else could be an quantifiable achievement.?
In case if someone has already asked this question and have answers, please direct me to the link. Thank you. Saving Changes...
Hi Ganesh, there is a lot in that question, but if you are interested in learning a lot about PMO's, I suggest you take a look at Laura Barnard's blog here:
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
PMO is the place where project/portfolio/programs functions are physically located (usually). Those functions has been defined as part of the strategy. Those functions has sense if and only if are aligned to strategical goals and objectives. PMO mission, vision, values have to be defined. With all these stuff you have to define why/when/what/who/how all these will be supported. After that you can define PMO KPIs. For example, if you said me "change request" I will ask you things like" what level? (portfolio/program/project)? why/what/how/when/who? about change request: define a process? execute a process? support a process?
...
1 reply by Ganesh Kumar
Mar 11, 2018 12:13 PM
Ganesh Kumar
...
Certainly Sergio, I get the point. Thanks for sharing.
Change requests are not an achievement in and of themselves. It always come back to the mandate and services provided by the PMO.
If the PMO's responsibility is portfolio management, then I'd look at ROI on the portfolio investments (taking into account the setup & run costs of the PMO itself).
Kiron
...
1 reply by Ganesh Kumar
Mar 11, 2018 12:18 PM
Ganesh Kumar
...
Thanks Kiron, agree with you. Will surely implement this part.
Saving Changes...
David FedorchakIT Specialist| Federal GovernmentVa, United States
I'd agree with Kiron. Change requests aren't particularly useful as any metric to measure anything (if there are a high number of requests is that a 'positive' thing because the PMO is active... a 'negative' thing because a lot of change is necessary... etc?). Instead, I like ROI as a potential metric. Also, deviations from plan would be useful. If projects are consistently 10% over planned budget.... 20% ahead of schedule (like that ever happens)... etc... these might indicate poor planning, lack of useful data on which to build a plan, overly optimistic or pessimistic estimates, execution problems, etc.
...
1 reply by Ganesh Kumar
Mar 11, 2018 12:19 PM
Ganesh Kumar
...
Thanks David, very valuable.
Saving Changes...
Ganesh KumarProgram ManagerBangalore., Karnataka, India
Mar 08, 2018 1:34 AM
Replying to Sante Delle-Vergini, PhD
...
Hi Ganesh, there is a lot in that question, but if you are interested in learning a lot about PMO's, I suggest you take a look at Laura Barnard's blog here:
Thanks Sante, for sharing such a valuable link. Saving Changes...
Ganesh KumarProgram ManagerBangalore., Karnataka, India
Mar 08, 2018 4:40 AM
Replying to Sergio Luis Conte
...
PMO is the place where project/portfolio/programs functions are physically located (usually). Those functions has been defined as part of the strategy. Those functions has sense if and only if are aligned to strategical goals and objectives. PMO mission, vision, values have to be defined. With all these stuff you have to define why/when/what/who/how all these will be supported. After that you can define PMO KPIs. For example, if you said me "change request" I will ask you things like" what level? (portfolio/program/project)? why/what/how/when/who? about change request: define a process? execute a process? support a process?
Certainly Sergio, I get the point. Thanks for sharing. Saving Changes...
Ganesh KumarProgram ManagerBangalore., Karnataka, India
Mar 08, 2018 6:37 AM
Replying to Kiron Bondale
...
Ganesh -
Change requests are not an achievement in and of themselves. It always come back to the mandate and services provided by the PMO.
If the PMO's responsibility is portfolio management, then I'd look at ROI on the portfolio investments (taking into account the setup & run costs of the PMO itself).
Kiron
Thanks Kiron, agree with you. Will surely implement this part. Saving Changes...
Ganesh KumarProgram ManagerBangalore., Karnataka, India
Mar 08, 2018 7:50 AM
Replying to David Fedorchak
...
I'd agree with Kiron. Change requests aren't particularly useful as any metric to measure anything (if there are a high number of requests is that a 'positive' thing because the PMO is active... a 'negative' thing because a lot of change is necessary... etc?). Instead, I like ROI as a potential metric. Also, deviations from plan would be useful. If projects are consistently 10% over planned budget.... 20% ahead of schedule (like that ever happens)... etc... these might indicate poor planning, lack of useful data on which to build a plan, overly optimistic or pessimistic estimates, execution problems, etc.
