I would be interested in hearing other's thoughts on this as well. I have yet to see a studio that had their process down so tight that they could easily farm out modules to off-shore (other than Andrew the Technical Consultant, I'm sure ;) ). Doing research online, most white-papers on the topic say that by the time you work through the communication issues, resolve errors and shore up security, the cost comes out about the same.
Chad -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Barry Beattie Sent: Friday, 4 March 2005 12:41 AM To: CFAussie Mailing List Subject: [cfaussie] hyperthetical: offshoring part of a project. hi all for Mark Jen-type reasons, I have a "hyperthetical" question. Say there's a decent-sized app to make. A couple of years worth. Say that part of it, about a third, is to be developed off shore. Basically one big module. Probably by a J2EE dev shop that would branch out into CF. Now, if the locally-built part is about a third finished when the offshoring starts, and has been developed using it's own "home-grown" MVC-type framework with heavy use of DHTML UI components (and mark-up)... (here's the question) ...what initial steps should be done to ensure as few integration and support heartaches as possible? What issues should be considered? Obviously, because this outsourced module will need in-house support (eg minor bug fixes and changes after sign-off), the documentation (all the way down to code comments and variable/method naming) needs to be up to scratch. anything else worth worring about? thanx b PS: even Oracle-type "follow the sun" development may be a possibility. --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/ --- You are currently subscribed to cfaussie as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
