Under-performing contractors on your team

[northernladuk]

I have seen some pretty poor contractors on site and often wondered how they got away with it. In some cases managers know they were bad but seemed reluctant to do anything about it either through it being more hassle to replace him or just not knowing what to do about it.

Now what happens if the manager of a team, say a PM with responsibility for say a team of BA's is a contractor and knows his stuff about contracts and one of the BA's isn't up to it. Anyone seen a manager, or been part of advising a client about the lack requirement to give notice or withdrawing work from a contractor in order to have him out the door fairly quickly to get someone in that can do the job?

Is this generally more hassle than it's worth or considered bad form so avoided unless absolutely necessary? Let them hang themselves to the client and let them deal with it or take the bull by the horns?

Edit : Just a theoretical question, not related to a situation.
Edit 2 : Accountant asked, it's not in the newbie guides, IANCOTBAC yadda yadda.

[TheCyclingProgrammer]

I haven't quite been in the situation you described, but have been in a position where the client wanted my input on who to keep on when the time came to downscale a project for budget reasons.

I was contracted as the lead developer on part of a project and part of that role was overseeing two other contractors. Now neither of these guys were bad. I had been involved in the process of hiring them so was able to ensure we could get half decent developers, client budget permitting.

But when the time came, I was happy to make a recommendation as to me it felt like my obligation as a lead developer and consultant on the project.

Which leads me onto my point. If I was in a bum on seat role I'd probably just keep my head down. But if I was a PM or hired in a consultancy or lead role, I would feel obligated to tell the client of anything I felt was impeding the progress of the project.

I'd leave it entirely for the client to deal with beyond that. And the scope of my criticisms would be strictly the person's work quality, not their general behaviour.

Having said that, if said person wasn't a contractor brought on for that specific project or was a client employee, I would probably leave it alone.

[BrilloPad]

If a permie messes up they get sacked. If a contractor messes up they get paid to fix it.

HTH

[TheCyclingProgrammer]

If a permie messes up they get sacked. If a contractor messes up they get paid to fix it.

HTH

That's not what my contract says!

(Practically, you're probably right, bugs in software development are normal and we do end up fixing them on the clock, but if I genuinely ****ed up, my contract stipulates that I will rectify at my own cost...you should see the additional clauses I add to my contract for iOS development relating to the Apple App Store review process!)

[BrilloPad]

That's not what my contract says!

(Practically, you're probably right, bugs in software development are normal and we do end up fixing them on the clock, but if I genuinely ****ed up, my contract stipulates that I will rectify at my own cost...you should see the additional clauses I add to my contract for iOS development relating to the Apple App Store review process!)

Most contracts are full of nonsense.

[eek]

Would this be a new BA who started at the client on Monday?

[Antman]

A friend told me about a contractor who wasn't up to the job and the programme manager wanted him out. It was a big deal, lots of metrics to be defined, email trail of tasks/timings to be recorded, comparison of similar tasks with others in team.

I can understand why people don't bother and just not renew but then they can't be bothered hiring someone else and all the hassle of interviews etc. either so the person ends up staying!

Perhaps this is (another) attraction of the bob consultancies, if you're not happy with someone speak to the engagement manager and whoosh there's somebody else sat there?

[psychocandy]

IMHO keep out of it at all costs. Let the client worry about they want to keep and who they don't. Get on with your own work and don't worry about anyone else.

I've been in same position where client asked me opinion on fellow contractor in team. Refused to get involved even though guy was a lazy arse. At the end of the day though, it was this guys livlihood, if he wanted to screw it up for himself then it was up to him and client to sort out.

It might not be the case, but nothing I hate more than contractors who think they're it and will happily screw others to get ahead. Thats what it gets seen as.

[The Spartan]

I worked at Sky with a lot of poor contractors and it was evident just how bad they were but nothing got done, I did ponder raising it but doubtless to say management wouldn't have listened. When I decided to end the gig there prematurely I did tell them how useless the Test Manager was, he was a contractor too and I hope to god that it's his first and last contract. I don't think he'll get sacked instead they'll make him a permie.

[d000hg]

That's not what my contract says!

(Practically, you're probably right, bugs in software development are normal and we do end up fixing them on the clock, but if I genuinely ****ed up, my contract stipulates that I will rectify at my own cost...you should see the additional clauses I add to my contract for iOS development relating to the Apple App Store review process!)

iOS dev you say... fancy working for £120/day?