Showing posts with label Issue Risk Management. Show all posts
Showing posts with label Issue Risk Management. Show all posts

Saturday, February 11, 2012

Role of the program in issue resolution: Project Management

Several times I had been told that the role of the program is to keep the ball rolling on tasks, and this meant little to me.

In a matrix organization, a key role of the functions is functional excellence. Several times, each functional member raises issues on other groups and the response to this issue by another group is usually a solution

Wrong!

The response to the issue by another group is another problem - rarely a solution.  Each functional team has what is often labelled as professional ego and it hurts to change their pas

Example, I need to fit this part and need 10 mm clearance. You have only 2 mm. Answer from a mating part group, even if I change you will have 3 mm besides I cant change it as it costs too much.

In most non-program situations, the conversation stalls here and in a muddle of competing tasks, functions move to easier tasks (not necessarily important). Often times, the issue gets resolved after long periods of inaction in a kind-of batch mode resulting in delays.

It requires a program team to get the experts together and strike a bargain with a unifying metric - the customer requirements - to move the program forward.

This is probably the key value add from program teams.



Subscribe to A.Karthiks blog

Sunday, March 29, 2009

PMO Maturity Model with respect to Project Issues: Value add from PMO


Most senior management expect the PMO to be aware of risks in projects based on (1) their interactions with project teams (2) cross project experiences



The 3 levels of maturity of a PMO are

1. Initial: The PMO is still getting to be aware of the programs/structure and processes. Further, the rapport with the program manager will determine the extent of the risk awareness

2. Reporting: The processes have been established. Techniques to effectively capture risk and resolve are commonly accepted by program teams and PMO. The project leaders are also confident of the methodology and the PMO is aware of the risks known to the project teams

3. Value added : The PMO has been well established and is working over a range of projects. Cross functional project experience enables the PMO to foresee risks in the program not self evident to the project teams.

Every organizations leadership wants PMOs to ramp up as fast as possible to Maturity level 3.