View Single Post
Old 09-02-2007, 01:41 PM  
Due
Confirmed User
 
Due's Avatar
 
Industry Role:
Join Date: Mar 2001
Location: Murrieta, CA
Posts: 3,620
I had very bad luck with programmers on outsourced jobs, we switched to use only fulltime inhouse programmers or working from home.
Biggest problems I see when using outsourced programmers is that they are not willing to commit fully to their projects, or they simply lie about what they are capable of.
When I start the work on something new with a programmer, I explain them in detail what the system should do, and how it should react, then I ask the programmer to do the system description and flow charts so I can approve it. It will help catching the first errors so programmers did not misunderstand my description, and start working on a completely different system.
Also it will reveal if the programmer is not really capable of the job many times
A good advice for people using outsourced programmers:
1: Make the programmer describe the system, and the functions
2: Add another 25% in development time needed for when it will actually be ready, if programmer say 4 weeks, count on 5 weeks.
3: Create mini goals, when should first beta be ready? How often do you need status reports.
4: Ask programmer to put a list online showing what he is working on, what is done, what contains bugs not yet fixed, best is to put dates on it, good to keep track of the progress. If you see good improvements on daily basis, dont nag the programmer too much, let him work
5: Never pay in full upfront. Pay possible an amount upfront, and then another when a mini goal is achieved, and the rest when code is complete. 25/25/50 or so in %
__________________
I buy plugs
Skype: Due_Global
/Due
Due is offline   Share thread on Digg Share thread on Twitter Share thread on Reddit Share thread on Facebook Reply With Quote