Talk of PPM, PMO and All Things Project

Welcome to this blog!

I hope to provide you with informational nuggets from my learnings and the successes/failures I have had in all things 'project'. I have worked across many industries and many cultures/countries, so most of my summarizations can be considered 'universal'.

Please send me an email if you have any special area of interest that you would like me to write on. If I can I will, if not, I will research and promise to send someone your way who can be of help.

Thursday, March 10, 2011

PMO's Role in Project Inception

The days of kicking off projects after some senior level discussions and some paperwork with the finance guys to allocate funds is becoming increasingly rare. For the most part, the days when a 'sponsor' expressed desire for a particular outcome, coupled with some paper allocation of funds which almost never got tracked against actuals, is over. That is not to say it does not happen; but factors such as increasing awareness of the high probability of project failure, leaner times and internet speed of adaptation have all demanded a greater degree of 'science' in the conception, definition and inception of projects.
While many organizations have incorporated a formalization of these activities through some documented process, most commonly this has come to be housed in the PMO function. The virtue of doing this is obvious - the 'pre-' and 'post-' factors can be articulated and analyzed in the same place so that the organization can do projects cheaper, faster, smarter. So what specifically does a PMO need to do for cheaper, faster, smarter, more business appropriate projects? I submit these are 6-fold:
1. WHY - Articulate the project's charter, what goals it seeks to achieve, what the business objectives of the project are
2. HOW - Enunciate the measures for its success i.e. how the project's end-result  will be measured: these are usually in terms of cost/time savings, market share increase, profitability increase or other measurable success factors
3. WHO will do the project , who is affected, who will make decisions, who will fund
4. WHERE will it be done and where it will have impact i.e. geographies, business units, customer types etc
5. WHEN - The time it will take to  complete the project, when it will be operational
6. WHAT - the scope of the work
While most of these may seem intuitive, you will be surprised how many projects lack clear definition on some or all of these 6 aspects rendering them either failed or at best unknown/unquantifiable in terms of their end-value in which case it is impossible to justify the cost/benefit of the project.

What often happens is that the sponsor is in a hurry to get the work started, and without a formal PMO to contend with may be tempted to or unconsciously bypass these critical efforts. It is the job of the PMO to ensure that it has enough executive level support to stand in the way of shortcuts and quick launches in favor of a more rationalized approach. Having said that, it is also the responsibility of the PMO to ensure that the process is not so lengthy and/or cumbersome that business/sponsors have real gripes about the value of the exercise. Most of all, PMO's need to close the circle of the project by doing a post- mortem on the business benefit of the project in addition to a post-mortem of the project execution itself and ensure that the benefits & lessons learned are communicated to all stakeholders in a timely fashion.

Finally, the PMO has a critical role to play in reporting back the financial performance of the project and eventually have ties into the business unit to see to the financial viability of the end-product’s throughout its life. This way, the PMO becomes an important stakeholder in also proposing the inception of new projects.

No comments:

Post a Comment