Project Management

Please login or join to subscribe to this thread

PM Roles differentiated by level of engagment

linkedin twitter facebook   Agile   Information Technology   PMO  
avatar
Michael Clark Manager of Corp IT PMO| EBSCO, Ind. Al, United States
Many of our departments state that their projects don't require PM engagement because they just need someone to coordinate with 3rd party vendors or they only want the PM to get them started, then self manage the work breakdown.

I've determined that there are 3 different roles that make sense for PM:
• Manager - typical PM as we all know it
• Specialist - front end PM work - kickoff meeting etc.
• Coordinator - coordination and communication

See If this makes sense:

120 people @ $14.4M all in
20% of work is projects =$2.88M in project costs
Bad Project Management = 60% delayed
Good Project Management = 20% delayed
Difference between Good/Bad = 40% of project time. = $1.152M

So it’s worth $1.152 to have “Good” Project Management for current CorpIT efforts.

Questions/Caveats:
• 20% project work is a “Guess”
• 40% diff from Bad to Good is a “guess”
• How do we define “Good” Project Management?

I need to define which roles we need at what ratios and then apply mapping to my current staff. The problem I am trying to solve is account for PM Resource assignments based on their effort/engagement on projects.

Many of our departments state that their projects don't require PM engagement because they just need someone to coordinate with 3rd party vendors or they only want the PM to get them started, then self manage the work breakdown.

Any insight to ways you may be doing this would be greatly appreciated.
Sort By:
avatar
Naomi Caietti Senior Project Manager | ePMO | Higher Education | Healthcare & IT| Linkedin.com/In/NaomiCaietti
Michael:
You can do this a variety of ways. Here's some ideas.

A. Best Practice Approach and Framework: Should be in place for to support B & C
You can define an organizational life-cycle approach for all departments around the approvals, process groups, resources and contract management. Key roles will be identified so you can track and manage a resource pool. You will have to define the entry point for a project. (See B)

B.Contract Management/Service Delivery Model:
See above, the framework can function as a contract management approach so contract manager can manage from a business group and request resources from functional managers including PMs. (A+B) or

C. Project Delivery Model/Hybrid:
See above, each project would get assigned a PM after contract approval and will assist contract manager with initiation. (A+C)

It's a challenge that needs executive input, and buy in. Let's see what others have to share.
...
1 reply by Michael Clark
Feb 27, 2017 10:41 AM
Michael Clark
...
Thank you for your response. This is very helpful.
avatar
Drew Craig Sr. Agile & Product Coach| Vanguard Philadelphia, Pa, United States
Michael,

"
Bad Project Management = 60% delayed
Good Project Management = 20% delayed"

How is this defined? How were these numbers reached? What does 'delayed' mean?

There ideally would be a contracts and vendor management department for those items. They are there to review SOW's and add advice for modifications required by the vendor prior to signing.
...
1 reply by Michael Clark
Feb 27, 2017 10:45 AM
Michael Clark
...
Andrew,

I was generalizing. "good" or "bad" is always subjective. I was referring to anything that would cause a project to experience a schedule variant or budget increase based on PM oversight.
avatar
Sergio Luis Conte Helping to create solutions for everyone| Worldwide based Organizations Buenos Aires, Argentina
I faced (and I am facing) this situations with my clients lot of times. My answer is: they do not need a project manager. What they need is somebody that help them to get the results needed. And that could be achieved by using project management skills. But if they do not visualize value to assing a project manager to the initiatives then it will not pay for it. One of the worst things I have found inside the project management community (and inside the PMI itself in some cases) is tried to demostrate that project manager are needed by numbers when on the other side (our clients) they have lot and tons of cases where with a project manager assigned things go wrong. So, you have to make your job to demostrate the value or to gain confidence again. But they do not need a project manager. Nobody needs a project manager.
avatar
Michael Clark Manager of Corp IT PMO| EBSCO, Ind. Al, United States
Feb 24, 2017 7:15 PM
Replying to Naomi Caietti
...
Michael:
You can do this a variety of ways. Here's some ideas.

A. Best Practice Approach and Framework: Should be in place for to support B & C
You can define an organizational life-cycle approach for all departments around the approvals, process groups, resources and contract management. Key roles will be identified so you can track and manage a resource pool. You will have to define the entry point for a project. (See B)

B.Contract Management/Service Delivery Model:
See above, the framework can function as a contract management approach so contract manager can manage from a business group and request resources from functional managers including PMs. (A+B) or

C. Project Delivery Model/Hybrid:
See above, each project would get assigned a PM after contract approval and will assist contract manager with initiation. (A+C)

It's a challenge that needs executive input, and buy in. Let's see what others have to share.
Thank you for your response. This is very helpful.
...
1 reply by Naomi Caietti
Feb 27, 2017 3:44 PM
Naomi Caietti
...
Michael:
Your're welcome. Also, looks like you are looking at Balanced Scorecard type indicators. It would be a good idea to flush this out since you can do this at many levels:

Project level - Each PM includes critical success factors
Program - Program can identify key performance indicators for projects, PMs, etc.
Organization - Balanced scorecard can be created for projects

There is a lot that goes into any metrics tracking; do a little research and discuss more internally.
avatar
Michael Clark Manager of Corp IT PMO| EBSCO, Ind. Al, United States
Feb 25, 2017 7:07 AM
Replying to Drew Craig
...
Michael,

"
Bad Project Management = 60% delayed
Good Project Management = 20% delayed"

How is this defined? How were these numbers reached? What does 'delayed' mean?

There ideally would be a contracts and vendor management department for those items. They are there to review SOW's and add advice for modifications required by the vendor prior to signing.
Andrew,

I was generalizing. "good" or "bad" is always subjective. I was referring to anything that would cause a project to experience a schedule variant or budget increase based on PM oversight.
avatar
Naomi Caietti Senior Project Manager | ePMO | Higher Education | Healthcare & IT| Linkedin.com/In/NaomiCaietti
Feb 27, 2017 10:41 AM
Replying to Michael Clark
...
Thank you for your response. This is very helpful.
Michael:
Your're welcome. Also, looks like you are looking at Balanced Scorecard type indicators. It would be a good idea to flush this out since you can do this at many levels:

Project level - Each PM includes critical success factors
Program - Program can identify key performance indicators for projects, PMs, etc.
Organization - Balanced scorecard can be created for projects

There is a lot that goes into any metrics tracking; do a little research and discuss more internally.

Please login or join to reply

Content ID:
ADVERTISEMENTS

"Wise men talk because they have something to say; fools, because they have to say something."

- Plato

ADVERTISEMENT

Sponsors