The fundamental is that you can't outsource skilled knowledge labour piecemeal. You either outsource everything, and provide a third party with a functional spe

The fundamental is that you can't outsource skilled knowledge labour piecemeal. You either outsource everything, and provide a third party with a functional specification, timings, and the financial means to fulfil those two, or you are, as they say, fucked. If you attempt to outsource individual components of a project to multiple physical locations in disparate timezones, you'll inevitably have a communications disconnect, and shit will hit fans. Developers need to talk to users need to talk to QA need to talk to management. Keep the lines open and clear, and everything goes smooth as a greased-up polecat in a cement mixer. Fail to do so, and everything suffers. In this scenario, it'd seem that the poor bastards in Uttar Pradesh or wherever-the-fuck don't have a clue as to what's going on. If they did, they'd probably do a halfway competent job. I've worked with QA teams in India and China in the past, and it's been an excellent experience - because we communicated with them non-stop. It would have been preferable to keep those elements on-site, however the parent company of the client we worked with were insistent that we utilise their resources - and because they managed them well, the arrangement was tenable. Anyway. Don't blame the outsourcee - blame yourself for either making a shitty decision or mismanaging the resources you've acquired.