[benandkelley]

Hi all,

I recently got put on a new project with a programmer who appears to be slow and not very dedicated to making the project happen. When I say slow, his coding does not meet deadlines, and then he won't stay late to try and keep the project on schedule. (As a programmer, I will get a project with months of work, and I'll work late if needed just to stay on schedule.) Each programmer is different, and each need a personalized schedule. However, how would you suggest I deal with this "slipping" programmer? I don't want to resort to threats. I try to be encouraging and enthusiastic.

I look forward to hearing your thoughts.

-Ben

PS: My role on the project is tech lead, so I'm responsible for the programmer to be on schedule.

[eyadams]

If you're Homer Simpson, you could just arrange for there to be tartar sauce in the cafeteria :-). However, here's what I would recommend, based on my experiences working for a couple of dot coms.

The first thing you should do is talk to him. Many programmers I have met assume that deadlines are arbitrary, and therefore safe to ignore. If that really isn't the case, you need to make that clear to him, and also make clear your expectation of long hours to meet deadlines. You should also ask if it would be possible to shift the work to another programmer. If he's as arrogant as most programmers, the suggestion that he's unable to perform a task will be a big motivator.

You could also see if there is the possbility of rewards for met deadlines. A "good job" can have an big impact; but cash speaks volumes.

However, you shouldn't rule out the possibility that you're going to have to be mean. A stern talking to from you might do the trick; more likely, however, it will be necessary for him to get a stern talking to from someone who can fire him. I've seen this approach work miracles, and would be surprised if the threat of losing his job in the current climate didn't motivate him to do better.

[madmacgames]

If even you as the head tech are also having to stay late just to keep projects "on schedule", then something is pretty wrong with your "schedule," and you're probably setting unrealistic deadlines -- you or whoever is setting the schedules and deadlines.

Now that said and soaking in, don't fall into the fundamental attribution error of blaming it all on the programmer (bad things happen to me because of external factors; bad things happen to others because of themselves) -- devoid of any evidence otherwise, we are inclined to believe this self serving bias.

So then if you are indeed in charge of the project, take on that role. Be a coach, be a leader, be a manager. Keep biases, etc in mind while talking with the programmer, and work with them to find the real causes of the problem. The solution then presents itself.

[timmerk]

Originally posted by benandkelley:
Hi all,

I recently got put on a new project with a programmer who appears to be slow and not very dedicated to making the project happen. When I say slow, his coding does not meet deadlines, and then he won't stay late to try and keep the project on schedule. (As a programmer, I will get a project with months of work, and I'll work late if needed just to stay on schedule.) Each programmer is different, and each need a personalized schedule. However, how would you suggest I deal with this "slipping" programmer? I don't want to resort to threats. I try to be encouraging and enthusiastic.

I look forward to hearing your thoughts.

-Ben

PS: My role on the project is tech lead, so I'm responsible for the programmer to be on schedule.

You're a tech lead!!!!!????? Outrageous! You better not let not your boss see your posts, or else you'll be fired in a second!

[Phil Sherry]

Originally posted by timmerk:
You're a tech lead!!!!!????? Outrageous! You better not let not your boss see your posts, or else you'll be fired in a second!

if you've got a problem - and judging by your similar posts towards this person, you have - use the PM system, rather than act like a child in this forum.

[benandkelley]

.