~ By Jason Becker
For openers, let's look at the meaning of the term "legitimise." Merriam-Webster says "To make legitimate." Enough said, right? If it were, then this would be a very short post.
This post is dedicated to a better understanding of what a project manager is and what a project manager does. Just as important, we will also be talking about what a project manager isn't.
I feel compelled because I have heard the following conversation take place in every company for which I have provided services, ever.
I feel like this project is important enough to have a full-time project manager and I think you [insert name here], would be the best choice. You have the technical knowledge and you know the scheduling tool so it should be a no-brainer for you. What do you think?
I think it is a great idea, but if I'm managing the project full-time, who will be responsible for my technical pieces of the project?
Well, I think there is enough time for you to do both. Just put in a few extra hours each week to update the schedule and we'll still be able to make the deadline…
Um, OK, I'll do my best…
Chances are, everyone reading this has heard or seen something similar, and with just a few short sentences you can see where this is going. In the case that you haven't been a victim of this kind of drive-by PM'ing, or know someone who has, I'll draw out the rest of the above project scenario in shorthand.
Before I can draw out the rest of the scenario, let's make a few assertions to set the stage.
OK. I'm going to make some generalisations here so let's assume for our purposes that the statements I am about to make apply most, but not all of the time.
This is partly due to the leadership figures' naiveté, partially due to the lack of project management skills in the technical talent, and partly due to timeslicing on an already overallocated resource (technical talent).
The thing that went most correctly in the above scenario was the leadership figure's recognition that he/she needed to apply some project management wisdom to the project. Although this was a misguided attempt, simple recognition is a good start.
While the leadership in this case has good intentions, he/she is not seasoned enough themselves to understand what "project management" really is.
The key technical person should have recognised that their technical responsibilities on a key initiative were far too demanding to allow him/her to timeslice.
Asking a key technical person to take on project management responsibilities is NOT a good idea unless that person is properly trained in project management disciplines and you are going to adjust your technical expectations from that person.
In other words, assigning a project manager is not magic, it is just like filling any other position in your organisation. Start by working with your HR people to open a job title and description that accurately reflects your needs and then prepare a budget for having projects properly managed in your organisation now and in the future.
Do your people, your company, and your project, a service and make sure you spend the proper amount of time in selecting the proper talent to manage your project.
Jason Becker, PMP, CPM, has 14 years of experience in designing, developing, and deploying enterprise-level software products for the Banking, Manufacturing, Real Estate, and Information Technology industries. He is an expert in project management surrounding software products development with an emphasis on disciplined delivery techniques and visionary software development methodologies. He is an experienced leader with skills in IT PMO set-up and management and strategic IT projects alignment.