<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Successful Projects &#187; Insourcing</title>
	<atom:link href="http://successfulprojects.net/category/insourcing/feed/" rel="self" type="application/rss+xml" />
	<link>http://successfulprojects.net</link>
	<description>Proving the ROI of Effective Project Managament</description>
	<lastBuildDate>Thu, 22 Oct 2009 15:37:06 +0000</lastBuildDate>
	
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>New view on Off-shoring</title>
		<link>http://successfulprojects.net/insourcing/new-view-on-off-shoring/</link>
		<comments>http://successfulprojects.net/insourcing/new-view-on-off-shoring/#comments</comments>
		<pubDate>Wed, 01 Nov 2006 17:51:37 +0000</pubDate>
		<dc:creator>jsweet</dc:creator>
				<category><![CDATA[Insourcing]]></category>

		<guid isPermaLink="false">http://successfulprojects.net/?p=4</guid>
		<description><![CDATA[Anyone who knows me, has ever talked to me or has read the Insourcing section of my blog knows that I have not been a big fan of off-shoring. I have spoken and written against the practice for years for many reasons but mainly because it has never succeeded in delivering on its promise of [...]]]></description>
			<content:encoded><![CDATA[<p>Anyone who knows me, has ever talked to me or has read the Insourcing section of my blog knows that I have not been a big fan of off-shoring. I have spoken and written against the practice for years for many reasons but mainly because it has never succeeded in delivering on its promise of better, faster and cheaper software.</p>
<p>So it is with no small sense of irony that I find myself managing the delivery of a strategic software product for a client who has elected to hire an off-shore firm to provide the software development resources for the effort. My client made this decision because they are a start-up without the necessary capital to go out and hire an entire team of American developers. So in order to get their latest version of software developed they have made the strategic decision to incorporate a Chinese development team.</p>
<p>The difference between my client and the majority of companies that have chosen off-shoring as a solution is that my client consciously made the decision to opt for lower cost over speed and quality. The problem with most off-shore projects is that the person who sold the project promised – whether implicitly or explicitly – that the customer could actually get better, faster and cheaper all at the same time. This misstatement of the potential of off-shore projects is one of the leading causes of the many stories we read about outright failures, cost overruns and projects delivered without meeting the specification – sounds a little like the majority of on-shore projects.</p>
<p>Cheaper is easy to accomplish and is achieved via off-shoring because off-shore developers simply make far less than American developers – the average Chinese software developer makes  $13,400 per year, the average Indian developer makes $10,300 while the average American developer makes around $80,000.</p>
<p>The hard truth is that better, faster and cheaper cannot exist in the same space and time regardless of whether you are using off-shoring or not. In the very best of circumstances a project could deliver better and faster simultaneously &#8211; though I have seen no evidence that these two can happen in an off-shore model. The only certain way to get better and faster is with dedicated on-site development resources who are very senior, have a great deal of domain experience and are very skilled at Agile delivery. Even with these ingredients delivering better and faster together is very challenging.</p>
<p>The achievement of better and faster requires a high performance, integrated team of developers, business analysts and testers working out of the same location as the customer all using a well honed agile methodology. This obviously doesn’t happen in an off-shore model since developers are half a world and up to 15 hours removed. Further, most off-shore teams have little successful experience with Agile methodologies.</p>
<p>All of that being said, I can tell you that I am having significant success with my off-shore team. We have successfully transitioned from a mentality of rigid adherence to CMMI to a more flexible acceptance of Agile principles. We have gone from a velocity of 4 – velocity is the number of productive hours within an 8 hour day &#8211; 3 months ago to a current velocity of 6.</p>
<p>None of this happened overnight and it has required a great deal of management work and iteration – in the true spirit of Agile – on how we run the team. The biggest contributor to the success of the team was that we brought them to American and had them work on site with the customer for a 3 months and when we sent them back we sent a highly experienced American Agile team lead with them to live and work in China for four months. I can assure you that without this last part the project would have failed. There is no replacement for this boots-on-the-ground team coach in the same time zone as the team.</p>
<p>Ultimately we have a blended team with all development and functional testing happening in China while business analysis and architecture occur here in the US. The other key component is that I have shifted my hours so that I overlap with the Chinese team in order to provide management oversight and to represent the customer. This isn’t a whole lot of fun for me and instead of working less I now feel like I work half-again as much but it is working.</p>
<p>The moral of the story is that off-shoring can work in the right situation but it has to involve a conscious decision to choose cheaper over faster and better and it must be well planned, well managed and well executed in order to achieve it.</p>
<p>I will post more later regarding a process you can uses to determine if the project you are running or are planning to undertake can benefit from an off-shore component.</p>
]]></content:encoded>
			<wfw:commentRss>http://successfulprojects.net/insourcing/new-view-on-off-shoring/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Outsourcing run amok</title>
		<link>http://successfulprojects.net/insourcing/outsourcing-run-amok/</link>
		<comments>http://successfulprojects.net/insourcing/outsourcing-run-amok/#comments</comments>
		<pubDate>Sun, 13 Aug 2006 01:34:32 +0000</pubDate>
		<dc:creator>jsweet</dc:creator>
				<category><![CDATA[Insourcing]]></category>

		<guid isPermaLink="false">http://successfulprojects.net/?p=9</guid>
		<description><![CDATA[On March 24th The outsourcing Weblog ran published a post that said,
With the many challenges facing large pharmaceutical companies nowadays there is a need to reduce development costs by as much as 30-40%, while at the same time significantly shortening development cycle times. If outsourcing is to meet these challenges, new models of collaborative and [...]]]></description>
			<content:encoded><![CDATA[<p>On March 24th The outsourcing Weblog ran published a post that said,</p>
<p>With the many challenges facing large pharmaceutical companies nowadays there is a need to reduce development costs by as much as 30-40%, while at the same time significantly shortening development cycle times. If outsourcing is to meet these challenges, new models of collaborative and cooperative working are needed. (http://www.outsourcing-weblog.com/50226711/research_and_markets_offers_outsourcing_clinical_development.php)</p>
<p>Frankly I disagree completely. The answer lies not in sending work and jobs overseas but in improving the way we do what we do here in America. Experience teaches us that just shipping work and jobs to a country whose standard of living is considerably less than ours does not automatically equate to gains in efficiency and reduction in development costs. In fact, there is plenty of evidence that projects done by Indian, Chinese and Russian firms don’t result in any real savings at all and in some cases cost more than if we had simply done those projects here in America.</p>
<p>The bottom line is that modern projects cannot be planned, managed and executed through stubborn reliance on outdated and inapplicable processes.  Today’s business evolves in an organic manner and projects have to be managed with this in mind &#8211; as functionality is developed and validated new and altered requirements are discovered and must be incorporated.  Traditional processes have no mechanism for dealing with this real-time evolution.</p>
<p>That’s where Insourcing comes in. Insourcing is more than just a catchy title.  Insourcing is a new way of approaching the work of projects.  It involves changing the fundamental paradigm of managing project based work.  Insourcing is about changing the way we think about the work we do and how we do it and, as a result, increasing performance and efficiency.</p>
<p>There are two hemispheres to insourcing.  The first hemisphere is about people, and about one’s ability to lead, motivate, inspire and reward.  This hemisphere deals with how to become an effective leader who can revolutionize the efficiency and productivity of staff members.</p>
<p>In order to solve the fundamental problems of software development we must first acknowledge that most leaders don’t do a very good job of leading.  Most leaders, if they were totally honest, would not be able to affirmatively answer, “Would you follow you as a leader?”</p>
<p>Effective leadership is a key factor in project success.   Every project has to have a leader.  The leader is responsible for the tone of the project and is the one person who can get the project staff to achieve remarkable results.</p>
<p>The second hemisphere is about process.  Insourcing is not process reengineering – it is a process revolution.  Agile processes begin to address this need but they go only so far and typically deal only with software development.  In order to increase efficiency and keep work in the US where it belongs we need to apply the principles of Agility to all work products not just to software development.</p>
]]></content:encoded>
			<wfw:commentRss>http://successfulprojects.net/insourcing/outsourcing-run-amok/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What the hell is Insourcing anyway?</title>
		<link>http://successfulprojects.net/insourcing/what-the-hell-is-insourcing-anyway/</link>
		<comments>http://successfulprojects.net/insourcing/what-the-hell-is-insourcing-anyway/#comments</comments>
		<pubDate>Sun, 13 Aug 2006 01:33:18 +0000</pubDate>
		<dc:creator>jsweet</dc:creator>
				<category><![CDATA[Insourcing]]></category>

		<guid isPermaLink="false">http://successfulprojects.net/?p=10</guid>
		<description><![CDATA[Depending on the research you read approximately 65% of the work done in American companies is project based.  The bad news is that most of these projects Fail. This is an indisputable fact. Many studies have been conducted over the past 10 years and they show with unanimity that the following three facts are true:
•    [...]]]></description>
			<content:encoded><![CDATA[<p>Depending on the research you read approximately 65% of the work done in American companies is project based.  The bad news is that most of these projects Fail. This is an indisputable fact. Many studies have been conducted over the past 10 years and they show with unanimity that the following three facts are true:<br />
•    American projects are more likely to be unsuccessful than successful<br />
•    Only about 1 out of 5 projects is likely to bring full satisfaction<br />
•    The larger the project the more likely the failure<br />
•    40% of new IS development projects are cancelled before completion at an estimated cost of $81 Billion annually<br />
•    33% of IS projects are “challenged” by cost/time overruns or changes in scope at an estimated cost of $59 Billion annually<br />
•    Failed and Challenged projects cost US companies and governments an estimated $145 billion annually<br />
Executives and decision makers in American companies have been faced with ghastly budget and schedule overruns of projects for years.  Estimates indicate that anywhere from $81 to $140 billion annually is lost as a result of poor project execution.  Given this, is there any wonder American executives have been searching for a solution?</p>
<p>Unfortunately, the solution du jour – off-shoring – has proven to be no better than the status quo.  The majority of off-shore projects experience cost and schedule overruns and the quality of work product being produced is sub par.</p>
<p>So what’s the solution?  Is there a way for American companies to solve the problems inherent in modern project based work?  And is there a way to solve these problems and get work and jobs back inside American companies?</p>
<p>The answer to both questions is yes and the solution is insourcing.  Insourcing is more than just a catchy title.  Insourcing is a new way of approaching the work of projects.  It involves changing the fundamental paradigm of managing project based work.  Insourcing is about changing the way we think about the work we do and how we do it and, as a result, increasing performance and efficiency.</p>
<p>Insourcing isn’t necessarily the antithesis of Outsourcing but it is a concept that if embraced can stem the unnecessary flow of jobs out of America and can help stop the hemorrhaging of money from companies coffers and shareholders pockets.</p>
]]></content:encoded>
			<wfw:commentRss>http://successfulprojects.net/insourcing/what-the-hell-is-insourcing-anyway/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
