Project Management

Please login or join to subscribe to this thread

Push back on assigning PM for a project

linkedin twitter facebook   Consulting   Energy and Utilities   Lessons Learned  
avatar
Joy Iyer Business Leader in the Hydrocarbons Sector, Engineering Manager, Project Manager| Paton Engineers and Constructors Mississauga, Ontario, Canada
Recently I encountered a situation where a Customer strongly suggested not assigning a PM to our project (in order to drive down costs), and instead assigning PM related tasks to the Technical Lead.

While I have a great deal of respect for the capabilities of our technical resources, I've generally observed that Technical Specialists are very good at focusing on technical specifications and tend to overlook budget and schedule variance.

In the present instance we managed to go down the path suggested by maintaining that the team composition is not solely decided by Customers and our company business controls have certain minimum requirements, one of which requires a PM to be assigned.

I am wondering if there are others in the community who have faced a similar situation? What are the arguments made in favor of not having a dedicated PM? How have you managed to avoid going down this rabbit hole?

Love to hear what others have to share...
Sort By:
< 1 2 3 >
avatar
Abolfazl Yousefi Darestani Manager, Quality and Continuous Improvement| Hörmann-TNR Industrial Doors Newmarket, Ontario, Canada
I agree with Sergio
< 1 2 3 >

Please login or join to reply

Content ID:
ADVERTISEMENTS

"You can make more friends in two months by becoming interested in other people than you can in two years by trying to get other people interested in you."

- Dale Carnegie

ADVERTISEMENT

Sponsors