Building the project team - postscript

In my last post, I suggested never under-estimating the work to be done in a project. Ensuring I followed my own advice, I have been trying to secure the services of a dedicated configuration manager - someone who can control the hundreds of individual software components that will be written or amended (perhaps many times) over the course of this project. Someone who can ensure that every last one is correctly allocated, signed out, signed back in, and included in each of the migration packages through testing and finally into production. It's an important role.

On Monday, it was mentioned that Mike was available soon, since his contract was due to end in a couple of weeks time. I immediately asked that he be assigned to my project.

"Ah!" said the HR guy, "we should first look to see if there is a permanent staff member who could fill the role".

"Okay, like who?" I replied, knowing that no-one with a career at the company would settle for that kind of job. It's the sort of thing only contractors specialise in.

"Well, Ray could do it; he's free at the moment".

I didn't know Ray, so we arranged for me to talk to his line manager, then yesterday I finally got to speak to Ray himself.

Not only did he not have anywhere near the level of experience I wanted, but he had no knowledge of the software he would be using, and had never done that kind of thing before. He also didn't fancy the idea.

Back to the drawing board. I went back to HR guy and said "Ray doesn't want the job, and he's not qualified anyway. Can I have Mike now?"

"Okay, fill in the usual form and I'll get it sorted".

Excellent, I thought, and quickly completed the form and emailed it.

Less than an hour later, came the reply :

"Sorry, but his current assignment manager has just renewed his contract and extended his assignment until July. What would you like us to do?"

Aaaaaarrrgggghhhh!!