article page
| 1
| 2
| 3
|
relying on IT provided not much advantage to the company.
The frustration in the business departments became so great that they started to ignore their IT groups and go it alone. As a result we have business managers that are no doubt completely qualified in their sphere making decisions on systems and who should manage their technical implementation. These are smart people, but with no experience in IT management or deployment. This can have just as unhappy results as the previous situation. In fact, this is exactly how the unfortunate PM mentioned earlier ended up in his current no-win situation.
So how should these folks select the "right" PM? Is there a better way? Here are some of my perspectives on this as a long-time project manager, program manager, decision-maker, and even, now and again, a client.
First, check the fundamentals, the candidate PM's skills, experience, qualifications etc. This should be an obvious step, but you may be surprised how often it is omitted. Now the candidates have been qualified against the basics how do you further minimize your project risk? Domain knowledge is a key consideration and preferably includes experience managing projects exactly like yours. Having successfully managed several similar projects is even better! Just because a person's job title is "PM" does not mean they are qualified to manage any type of project.
This is a problem, particularly in the IT industry. There is a view that all IT project managers are the same. Not true. I would describe myself as a software development and software package implementation PM. Please do not assign me an IT infrastructure project, like an IT network design and deployment project. Don't ask me to manage desktop setups and server deployments. Yes, these come under the umbrella of IT Projects, but they are not in my core skill set. Sure, I could quickly learn, but the project will