<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Offshore development: aim for it, even if you never go there</title>
	<atom:link href="http://www.peterkretzman.com/2008/02/19/offshore-development-aim-for-it-even-if-you-never-go-there/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.peterkretzman.com/2008/02/19/offshore-development-aim-for-it-even-if-you-never-go-there/</link>
	<description>Intensely practical tips on information technology management, by Peter Kretzman</description>
	<lastBuildDate>Fri, 19 Mar 2010 17:07:45 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: PK</title>
		<link>http://www.peterkretzman.com/2008/02/19/offshore-development-aim-for-it-even-if-you-never-go-there/comment-page-1/#comment-8589</link>
		<dc:creator>PK</dc:creator>
		<pubDate>Thu, 20 Aug 2009 02:20:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.peterkretzman.com/2008/02/19/offshore-development-aim-for-it-even-if-you-never-go-there/#comment-8589</guid>
		<description>Thanks for your comment, Val. It would have been more germane, though, if it had addressed the actual point of my post, rather than simply touting the well-known and widely accepted notion of development cost savings obtained from offshoring development.  This disconnect is especially notable if you represent a vendor in that space.

The thrust of your comment was that the cost savings are compelling and worthy of investigation. The thrust of my post, however, had nothing to do with the development cost and everything to do with the seldom-seen readiness of internal teams to absorb systems and components built by outsiders (either down the street or across the ocean).  I summed up: &quot;So here’s my point: creating crisp handoffs, per the skeleton outline above, is something you absolutely must do if you ever hope to outsource. &quot;  

It seems that you somehow read my post as categorically opposing offshoring; I don&#039;t, which is why I wrote this post to explain my stance more completely. While I do have some healthy skepticism about offshore development, I have indeed seen it work effectively.  Instead, I choose to emphasize the&lt;em&gt; internal preparation&lt;/em&gt; needed long before a company can go down that path, because that is a prerequisite that is often missed amid the shiny appeal of dev cost savings.</description>
		<content:encoded><![CDATA[<p>Thanks for your comment, Val. It would have been more germane, though, if it had addressed the actual point of my post, rather than simply touting the well-known and widely accepted notion of development cost savings obtained from offshoring development.  This disconnect is especially notable if you represent a vendor in that space.</p>
<p>The thrust of your comment was that the cost savings are compelling and worthy of investigation. The thrust of my post, however, had nothing to do with the development cost and everything to do with the seldom-seen readiness of internal teams to absorb systems and components built by outsiders (either down the street or across the ocean).  I summed up: &#8220;So here’s my point: creating crisp handoffs, per the skeleton outline above, is something you absolutely must do if you ever hope to outsource. &#8221;  </p>
<p>It seems that you somehow read my post as categorically opposing offshoring; I don&#8217;t, which is why I wrote this post to explain my stance more completely. While I do have some healthy skepticism about offshore development, I have indeed seen it work effectively.  Instead, I choose to emphasize the<em> internal preparation</em> needed long before a company can go down that path, because that is a prerequisite that is often missed amid the shiny appeal of dev cost savings.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Val Jelinic</title>
		<link>http://www.peterkretzman.com/2008/02/19/offshore-development-aim-for-it-even-if-you-never-go-there/comment-page-1/#comment-8587</link>
		<dc:creator>Val Jelinic</dc:creator>
		<pubDate>Wed, 19 Aug 2009 14:13:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.peterkretzman.com/2008/02/19/offshore-development-aim-for-it-even-if-you-never-go-there/#comment-8587</guid>
		<description>Interesting comments Peter, however, I still think the main point is being overlooked here.

Today, especially in this time of financial crisis and economic recession, outsourcing portions of business requirements to offshore companies is becoming more &amp; more the norm.

Greater investment to return ratio, customised teams to perform the work without the expensive permanent staffing &amp; management and a quality control of the product/service that is greatly improving, this fast-growing alternative is showing that what was once considered to be high risk and hard-to-control is fast becoming and alternative that cannot be ignored.

Small, flexible teams operating under controlled supervision by experienced managers with cultural and technological experience is proving to be a valuable commodity. 

Large software houses are cumbersome with in-flexible internal processes and fixed overheads that must make high margin to cover costs, hence, their products/services prices are greatly inflated. 

One such Swiss based company recently quoted 700 man hours over 6months for development work of a web-based application to the tune of CHF750,000!! Something which an offshore software development company would be able to do for 1/10 of the price (dependant on location and the specifications of course!) and possibly a shorter delivery time. 

These savings are hard to ignore when the financial pinch is being felt everwhere.

For SME&#039;s and Start-Ups everywhere the question is not whether or not to consider an offshore software development as an alternative to a large, established software house but which alternative to choose from!

The market is lush with choices for an alternative and many savings to be had. Worthy of further investigation no?

Val Jelinic

Business Development Manager
MNG-Europe SA
Fribourg, Switzerland</description>
		<content:encoded><![CDATA[<p>Interesting comments Peter, however, I still think the main point is being overlooked here.</p>
<p>Today, especially in this time of financial crisis and economic recession, outsourcing portions of business requirements to offshore companies is becoming more &amp; more the norm.</p>
<p>Greater investment to return ratio, customised teams to perform the work without the expensive permanent staffing &amp; management and a quality control of the product/service that is greatly improving, this fast-growing alternative is showing that what was once considered to be high risk and hard-to-control is fast becoming and alternative that cannot be ignored.</p>
<p>Small, flexible teams operating under controlled supervision by experienced managers with cultural and technological experience is proving to be a valuable commodity. </p>
<p>Large software houses are cumbersome with in-flexible internal processes and fixed overheads that must make high margin to cover costs, hence, their products/services prices are greatly inflated. </p>
<p>One such Swiss based company recently quoted 700 man hours over 6months for development work of a web-based application to the tune of CHF750,000!! Something which an offshore software development company would be able to do for 1/10 of the price (dependant on location and the specifications of course!) and possibly a shorter delivery time. </p>
<p>These savings are hard to ignore when the financial pinch is being felt everwhere.</p>
<p>For SME&#8217;s and Start-Ups everywhere the question is not whether or not to consider an offshore software development as an alternative to a large, established software house but which alternative to choose from!</p>
<p>The market is lush with choices for an alternative and many savings to be had. Worthy of further investigation no?</p>
<p>Val Jelinic</p>
<p>Business Development Manager<br />
MNG-Europe SA<br />
Fribourg, Switzerland</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Get multiple arrows for that quiver: selective and competitive outsourcing</title>
		<link>http://www.peterkretzman.com/2008/02/19/offshore-development-aim-for-it-even-if-you-never-go-there/comment-page-1/#comment-8546</link>
		<dc:creator>Get multiple arrows for that quiver: selective and competitive outsourcing</dc:creator>
		<pubDate>Wed, 06 May 2009 16:53:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.peterkretzman.com/2008/02/19/offshore-development-aim-for-it-even-if-you-never-go-there/#comment-8546</guid>
		<description>[...] I&#8217;ve written before (&#8221;Offshore development: target the destination, even if you never go there&#8220;), the reality of the CTO/CIO&#8217;s life is to be constantly challenged to produce more. [...]</description>
		<content:encoded><![CDATA[<p>[...] I&#8217;ve written before (&#8221;Offshore development: target the destination, even if you never go there&#8220;), the reality of the CTO/CIO&#8217;s life is to be constantly challenged to produce more. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Canaries in the coal mine: Why your IT department may be in worse shape than you think</title>
		<link>http://www.peterkretzman.com/2008/02/19/offshore-development-aim-for-it-even-if-you-never-go-there/comment-page-1/#comment-8544</link>
		<dc:creator>Canaries in the coal mine: Why your IT department may be in worse shape than you think</dc:creator>
		<pubDate>Mon, 04 May 2009 18:35:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.peterkretzman.com/2008/02/19/offshore-development-aim-for-it-even-if-you-never-go-there/#comment-8544</guid>
		<description>[...] There’s no crisp handoff of new production code to the operations group, and no formal Operations Acceptance Test (OAT).   Putting code into production needs to be a big [...]</description>
		<content:encoded><![CDATA[<p>[...] There’s no crisp handoff of new production code to the operations group, and no formal Operations Acceptance Test (OAT).   Putting code into production needs to be a big [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
