Project to Operations

Information Technology

Pier Luigi Calabria Project Manager| INFORM Institut für Operations Research und Management GmbH, Aachen, Germany Aachen, Germany

Just for my awareness, how many of you, PMs, work in a reality where the output of the project is actually given "back" to the PM that then is renamed Service Manager? So, basically, you may do a 1-year project to produce a delivery, then you keep the system alive doing maintenance and change management for 10 years or so.

Which are the pros and cons of this setup?

For example, a pro, for me, is if the PM delivers a very bad project, he then keeps the dust on his desk and must sort it out, not leaving the issues to someone else. Of course, you may argue that if a PM delivers a bad result, he's not such a great PM.

Your views on this matter?

Posted: Sep 5, 2018 2:58 AM

Sort By:

< 1 2 >

RAJESH K L Project Manager, PMP| Bharat Electronics, Bengaluru, India Bengaluru, Karnataka, India

Sep 05, 2018 12:04 PM

Replying to Steve Ratkaj

...

This happed to myself. Was DPM/ PM for a while, and then ended up being the "In-service manager. As typical, the project staff left many "loose ends" before I came on board. It was good in a sense, that as the PM, I was able to mitigate the impacts of many mistakes/ shortcuts the project had made, but at the same time, the staff had been greatly reduced, and there was a lot of "rework" of technical documents that had to be done with a very limited staff that I inherited as the In-service manager.

Thanks steve for your reply and insights into the issue.

Posted: Sep 6, 2018 1:48 AM

< 1 2 >

Please login or join to reply

Project to Operations

Sponsors

Vendor Events

Guessing is not a strategy: How to build decision velocity with AI and real-time data

Newsletters