In-house Development Or Outsourcing

If you own a website that related to offshore development you are welcome to participate in our website.

Join our partner list

Software Development online portal

Web Development Forum

Article - Offshore Development And In-house Development Or Outsourcing on Web Development Forum

Website about Offshore Development - Software Development portal. Other useful information: This isn't something covered in huge detail in many of the standard agile texts so I thought it was worth it's own topic. Patterns & practices teams are" / Just to be completely clear I am not anti offshore development but my experience is that there are definitely good and bad ways to do it and there are taxes associated with doing it that aren’t always taken into account. J2EE: EJB, JSP, Servlets, JSF, JSTL, JCA, JMS, JTA, JNDI, JDBC, JMX, RMI, etc. Frameworks: Struts, Hibernate, JPA, iBATIS, JBoss AOP, Spring, JSF, AJAX, GWT, YUI, Flex/Flash, JUnit, and Jakarta common libraries. Integration: Web Services on Axis and WebMethods; as well as the Web Service Standards such as SOAP, WSDL and UDDI.

For you information - Given The Rapid Growth Of This Sector, Several Companies Have Started To Use Offshore Development In China, India And Other Countries With A Lower Cost Per Developer Model. Several New Web 2.0 Platforms And Sites Are Now Developed Offshore While Management Is Located In Western Countries.

Choosing An Agile Process - Part 4: Offshore Development | #2782 - Agile Software Development, Patterns And Practices For Building Microsoft .NET Appl - Choosing an agile process - Part 4: Offshore development | #2782 - Agile software development, patterns and practices for building Microsoft .NET applications. Choosing an agile process - Part 4: Offshore development Patterns & practices teams are usually distributed in some way. This is something that we’ve been doing for a while and have come up with a few things that work and a bunch that, in my opinion, clearly do not. As part of some work I’ve been doing to clarify the best practices we use I started researching some best practices for running distributed and offshore teams. Co-locate as much as possible: Whenever possible, co-locate your entire team in one location. If this is not possible then plan for team members to spend periods traveling and working at the main or offshore site, especially at the start of a project - the first few iterations - when key architectural/design decisions will be made. Align the team locations: The more offshore locations your team has the higher the communication barriers become. When using offshore team members group them into sub-teams aligned by feature (see below). #2782 Home About Publications Talks Recommended Reading Tuesday, January 15, 2008 – 5:44 am This isn’t something covered in huge detail in many of the standard agile texts so I thought it was worth it’s own topic. I compiled this list after reading a lot and thinking about some of the things we were doing. Think of these more as suggestions rather than proven practices used today at p&p: Time zones add further tax: One of the hardest aspects of distributed collaboration is working across time zones. Try to minimize the distance between the team locations as much as possible and try to establish ‘core working hours’ that all members can adhere to.