Средство программирования Outsource

Offshore Software Development - Evolution of Value Chain

Вы должны услышать все виды теорий на положении offshore развития средства программирования by now. Возможно вы испытывали его firsthand? Я верю offshore обсуждению развития средства программирования, учя возможности и развитие будет продолжаться на некоторое время. Оно одной из причин, котор я создал это место: Плоское развитие средства программирования мира.

Наиболее часто это место общается с здесь и теперь offshore развития средства программирования. Оно предназначает обеспечить окружающую среду для немедленно справки и обмена общины. В этом столбе, я хотел был бы сказать рассказ на развитии значения в развитии средства программирования. Оно fictional, но оно основано на поистине случаях. Я любознательон для того чтобы услышать ваши мысли. Здесь рассказ….

В так расстоянии за, развития компании стержня обусловливает там будет потребность рынка для чисто backend обслуживаний развития средства программирования. Вы знаете, не конструкция поверхности стыка потребителя, не испытывать usability - справедливый функциональный программировать. Их клиентов мнение часто что-то подобное: «справедливая программа функциональность пожалуйста - здесь мы хотим ее сделать, теперь делает она работу». The client doesn’t particularly care if it is Smalltalk or C or C++ or .Net or PHP or Java or ASP or TCL or PERL or Ruby on Rails or New ShinyLanguage. They just want it to work and and work well in their environment.

One day, web development company receives a request for proposal for a new client software development project. For this particular project, web development company creates a proposal based on resources of one developer architect and full-time employee(s) and/or one local software development programming contractor(s) to produce the software. In order to determine the proposal price of the project, development company looks at essentially two factors: perceived delivered value and operational cost. For value, the web development company is essentially delivering on two points: strategic design of “functionality” from the software architect and tactical implementation of the programming language/code. Also, included in the price of the project are applicable operational cost factors - monthly office space rent, employee salaries, contractor hourly rates, phones, internet access, insurance, etc.

Proposal Cost = $xyz

Client accepts and everyone is reasonably happy. Time rolls on, spring arrives, the sun shines, leaves turn colors, it rains, it snows.

Now, if web development services are inline with most other types of businesses, project fees should decrease over time. Not fall like the rain, but essentially the same service costs should decrease over time. Right? Simply put, client should expect to pay less than $xyz in a year from now for the same type of service. Notice this expectation has nothing to do with software quality determinations or h-1b visa or offshore software vs. inshore vs. rural source. There is an expectation from client that costs should decrease over time.

Now, if the paying client expects prices to decrease over time, something has to give for the web development company. Perhaps, the web development company needs to lower operational costs or promote an alternative, more cutting edge technical solution to keep project fees the same. (Selling the latest b/leading edge technology without significant increase in functional value just to maintain rates to clients is unethical and is partly the fault of the client for buying it. It is also a different topic entirely.)

To cut operational costs, web developer company decides to keep arcitectural design in-house and offshore the tactical development.

Cost = $xyz * .35

Cost is 35% lower and the client accepts the proposal.

Client wins- web development company wins - offshore software developer(s) wins. Win * 3. So, who doesn’t “win”? Frankly, the person who is at risk of negative change is the one who doesn’t see evolution trend the software development value chain. In this story, it is the developer who refuses to see offshore software developers as a viable option for tactical level programming. In this story, the local tactical programmer’s value is decreasing when web development company is attempting to “win” new engagements. It follows a similar trend line to the the client’s expectation of lower cost over time.

Now, hopefully, there are many openings to discuss this story on all kinds of levels. For example, a point could be made that web development company could focus on providing education resources to local tactical developers. This will increase skill sets which should lead to development time savings. Time savings implies lower cost. Or, client should not expect prices to lower over time or this story is based on waterfall development process and doesn’t jive with XP or Agile or suggesting software modelling tools to generate tactical code or somehow fit the old build vs. buy talk into the mix. But, I’ll leave these and many more openings to you. I attempted to write the story from an unbiased perspective, because I’m interested in hearing your thoughts. Leave comment or trackback with your thoughts.

PS - Check out the Cynosural blog from JosephDP who has some interesting posts regarding offshore software development.

This entry was posted on Wednesday, April 19th, 2006 at 8:01 am and is filed under Industry. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.