<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Shadow IT:  The Good, The Bad, and the Ugly</title>
	<atom:link href="http://vaughanmerlyn.com/2008/07/22/shadow-it-the-good-the-bad-and-the-ugly/feed/" rel="self" type="application/rss+xml" />
	<link>http://vaughanmerlyn.com/2008/07/22/shadow-it-the-good-the-bad-and-the-ugly/</link>
	<description>Vaughan Merlyn on the Changing Role of the IT Organization</description>
	<lastBuildDate>Wed, 07 Dec 2011 19:30:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: zoki</title>
		<link>http://vaughanmerlyn.com/2008/07/22/shadow-it-the-good-the-bad-and-the-ugly/#comment-1874</link>
		<dc:creator><![CDATA[zoki]]></dc:creator>
		<pubDate>Fri, 21 Jan 2011 14:33:27 +0000</pubDate>
		<guid isPermaLink="false">http://itorganization2017.wordpress.com/?p=311#comment-1874</guid>
		<description><![CDATA[I was more than happy to find this net-site.I needed to thanks in your time for this excellent learn!! I undoubtedly having fun with every little little bit of it and I have you bookmarked to take a look at new stuff you blog post.]]></description>
		<content:encoded><![CDATA[<p>I was more than happy to find this net-site.I needed to thanks in your time for this excellent learn!! I undoubtedly having fun with every little little bit of it and I have you bookmarked to take a look at new stuff you blog post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Micro ETL in the PowerPivot age &#171; Gobán Saor</title>
		<link>http://vaughanmerlyn.com/2008/07/22/shadow-it-the-good-the-bad-and-the-ugly/#comment-1604</link>
		<dc:creator><![CDATA[Micro ETL in the PowerPivot age &#171; Gobán Saor]]></dc:creator>
		<pubDate>Fri, 20 Aug 2010 18:23:37 +0000</pubDate>
		<guid isPermaLink="false">http://itorganization2017.wordpress.com/?p=311#comment-1604</guid>
		<description><![CDATA[[...] you with cleansed and understandable data , you&#8217;ll be faced with integrating external or shadow-IT data (probably one of the main reasons why PowerPivot appeals); again you&#8217;ll either need IT [...]]]></description>
		<content:encoded><![CDATA[<p>[...] you with cleansed and understandable data , you&#8217;ll be faced with integrating external or shadow-IT data (probably one of the main reasons why PowerPivot appeals); again you&#8217;ll either need IT [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: these 5 great articles will help you deal with &#8220;shadow IT&#8221; &#124; Wazoo Enterprises</title>
		<link>http://vaughanmerlyn.com/2008/07/22/shadow-it-the-good-the-bad-and-the-ugly/#comment-1451</link>
		<dc:creator><![CDATA[these 5 great articles will help you deal with &#8220;shadow IT&#8221; &#124; Wazoo Enterprises]]></dc:creator>
		<pubDate>Tue, 25 May 2010 12:06:50 +0000</pubDate>
		<guid isPermaLink="false">http://itorganization2017.wordpress.com/?p=311#comment-1451</guid>
		<description><![CDATA[[...] Vaughan Merlyn has a few great writeups about this force in the IT world, but this piece provides some clear [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Vaughan Merlyn has a few great writeups about this force in the IT world, but this piece provides some clear [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: praveen nair</title>
		<link>http://vaughanmerlyn.com/2008/07/22/shadow-it-the-good-the-bad-and-the-ugly/#comment-488</link>
		<dc:creator><![CDATA[praveen nair]]></dc:creator>
		<pubDate>Tue, 09 Dec 2008 13:06:16 +0000</pubDate>
		<guid isPermaLink="false">http://itorganization2017.wordpress.com/?p=311#comment-488</guid>
		<description><![CDATA[pic is superb]]></description>
		<content:encoded><![CDATA[<p>pic is superb</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex</title>
		<link>http://vaughanmerlyn.com/2008/07/22/shadow-it-the-good-the-bad-and-the-ugly/#comment-363</link>
		<dc:creator><![CDATA[Alex]]></dc:creator>
		<pubDate>Tue, 12 Aug 2008 14:23:58 +0000</pubDate>
		<guid isPermaLink="false">http://itorganization2017.wordpress.com/?p=311#comment-363</guid>
		<description><![CDATA[I found your site on technorati and read a few of your other posts. Keep up the good work. I just added your RSS feed to my Google News Reader. Looking forward to reading more from you down the road!]]></description>
		<content:encoded><![CDATA[<p>I found your site on technorati and read a few of your other posts. Keep up the good work. I just added your RSS feed to my Google News Reader. Looking forward to reading more from you down the road!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: IT Maturity Sanity Check - How Do You Stack Up? &#171; IT Organization Circa 2017</title>
		<link>http://vaughanmerlyn.com/2008/07/22/shadow-it-the-good-the-bad-and-the-ugly/#comment-362</link>
		<dc:creator><![CDATA[IT Maturity Sanity Check - How Do You Stack Up? &#171; IT Organization Circa 2017]]></dc:creator>
		<pubDate>Mon, 11 Aug 2008 12:54:11 +0000</pubDate>
		<guid isPermaLink="false">http://itorganization2017.wordpress.com/?p=311#comment-362</guid>
		<description><![CDATA[[...] is a significant &#8220;non-formal&#8221; - i.e., shadow IT spend that is outside the IT budget.  Shadow IT typically occurs as a natural response to a void [...]]]></description>
		<content:encoded><![CDATA[<p>[...] is a significant &#8220;non-formal&#8221; &#8211; i.e., shadow IT spend that is outside the IT budget.  Shadow IT typically occurs as a natural response to a void [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: IT Organization Design and the Value Disciplines &#171; IT Organization Circa 2017</title>
		<link>http://vaughanmerlyn.com/2008/07/22/shadow-it-the-good-the-bad-and-the-ugly/#comment-341</link>
		<dc:creator><![CDATA[IT Organization Design and the Value Disciplines &#171; IT Organization Circa 2017]]></dc:creator>
		<pubDate>Thu, 24 Jul 2008 10:06:53 +0000</pubDate>
		<guid isPermaLink="false">http://itorganization2017.wordpress.com/?p=311#comment-341</guid>
		<description><![CDATA[[...] and the Value&#160;Disciplines  Posted on July 24, 2008 by itorganization2017   My recent post on Shadow IT: The Good , The Bad and The Ugly solicited an interesting comment about organization design and the placement of application [...]]]></description>
		<content:encoded><![CDATA[<p>[...] and the Value&nbsp;Disciplines  Posted on July 24, 2008 by itorganization2017   My recent post on Shadow IT: The Good , The Bad and The Ugly solicited an interesting comment about organization design and the placement of application [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: itorganization2017</title>
		<link>http://vaughanmerlyn.com/2008/07/22/shadow-it-the-good-the-bad-and-the-ugly/#comment-340</link>
		<dc:creator><![CDATA[itorganization2017]]></dc:creator>
		<pubDate>Wed, 23 Jul 2008 17:54:50 +0000</pubDate>
		<guid isPermaLink="false">http://itorganization2017.wordpress.com/?p=311#comment-340</guid>
		<description><![CDATA[Great question, thanks!  I think there are several issues wrapped up in this - let me take them one by one:
1. Should application development and application support be together?

There&#039;s always an &quot;it depends&quot; aspect to this, and no organization model is perfect for all time.  In fact, it has been said that every organization design contains the seeds of its own destruction, which is why we tend to see the cycles of centralize-decentralize.  With those caveats, when development is constantly interrupted by support needs, productivity and quality suffer, so there is an argument to keep them separate.  Having said that, cycling people between development and support groups (i.e., developers take a turn supporting what they&#039;ve developed) is a good practice.

2. Should either application development or application support be located in the business rather than in an IT organization?  There are arguments for locating support in the business, though this is not the most common practice.  Having said that, we have to be careful in defining what is meant by, and what is the scope of support.  I think of support as being strictly about helping users to use a system effectively, and dealing with bugs and fixes.  Anything beyond that is development.  This is an important distinction as &quot;support&quot; has a way of becoming a back door into development - a quick way to get stuff done without going through the disciplines common to a development organization.  This is a slippery slope and usually ends up in &quot;tears before bedtime&quot; as my wife likes to say.

The other issue is tiers of support - Tier 1 typically means basic handholding, Tier 2 means some level of real problem solving and analysis, and Tier 3 means deep problem solving.  It makes a lot of sense to put Tier 1 in the business - if possible, even turn it into a self-service model.  Tier 2 is typically in IT but separate from development, and Tier 3 is often in development.

I think there are rarely good reasons to put development in the business, except for high maturity organizaitons, or if the development needs of a given business unit are TRULY unique (i.e., not just becasue the business likes to think they are different!)

Having said all of that, if you really are lower maturity, I&#039;d be inclined to centralize as much as possible under IT so as to deploy good practices, common methods and disciplines, and look to migrate those things that can be migrated later on, once those disciplines have been internalized.]]></description>
		<content:encoded><![CDATA[<p>Great question, thanks!  I think there are several issues wrapped up in this &#8211; let me take them one by one:<br />
1. Should application development and application support be together?</p>
<p>There&#8217;s always an &#8220;it depends&#8221; aspect to this, and no organization model is perfect for all time.  In fact, it has been said that every organization design contains the seeds of its own destruction, which is why we tend to see the cycles of centralize-decentralize.  With those caveats, when development is constantly interrupted by support needs, productivity and quality suffer, so there is an argument to keep them separate.  Having said that, cycling people between development and support groups (i.e., developers take a turn supporting what they&#8217;ve developed) is a good practice.</p>
<p>2. Should either application development or application support be located in the business rather than in an IT organization?  There are arguments for locating support in the business, though this is not the most common practice.  Having said that, we have to be careful in defining what is meant by, and what is the scope of support.  I think of support as being strictly about helping users to use a system effectively, and dealing with bugs and fixes.  Anything beyond that is development.  This is an important distinction as &#8220;support&#8221; has a way of becoming a back door into development &#8211; a quick way to get stuff done without going through the disciplines common to a development organization.  This is a slippery slope and usually ends up in &#8220;tears before bedtime&#8221; as my wife likes to say.</p>
<p>The other issue is tiers of support &#8211; Tier 1 typically means basic handholding, Tier 2 means some level of real problem solving and analysis, and Tier 3 means deep problem solving.  It makes a lot of sense to put Tier 1 in the business &#8211; if possible, even turn it into a self-service model.  Tier 2 is typically in IT but separate from development, and Tier 3 is often in development.</p>
<p>I think there are rarely good reasons to put development in the business, except for high maturity organizaitons, or if the development needs of a given business unit are TRULY unique (i.e., not just becasue the business likes to think they are different!)</p>
<p>Having said all of that, if you really are lower maturity, I&#8217;d be inclined to centralize as much as possible under IT so as to deploy good practices, common methods and disciplines, and look to migrate those things that can be migrated later on, once those disciplines have been internalized.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave</title>
		<link>http://vaughanmerlyn.com/2008/07/22/shadow-it-the-good-the-bad-and-the-ugly/#comment-339</link>
		<dc:creator><![CDATA[Dave]]></dc:creator>
		<pubDate>Wed, 23 Jul 2008 17:34:47 +0000</pubDate>
		<guid isPermaLink="false">http://itorganization2017.wordpress.com/?p=311#comment-339</guid>
		<description><![CDATA[In this case of IT, where does Application Support lie in the organization? We have application support (how do I do XYZ in an appplicaiton? I need a new company set up in application XYZ.)  reporting up to &quot;Accounting&quot;, while the Application Development (make these code changes, write these interfaces) rolling up to IT.

I would not consider us a very mature IT company, btu this divide in application support vs. application development seems to work &quot;OK&quot;. Some times we march to the same beat, and other times we do not.

Your thoughts?

Dave]]></description>
		<content:encoded><![CDATA[<p>In this case of IT, where does Application Support lie in the organization? We have application support (how do I do XYZ in an appplicaiton? I need a new company set up in application XYZ.)  reporting up to &#8220;Accounting&#8221;, while the Application Development (make these code changes, write these interfaces) rolling up to IT.</p>
<p>I would not consider us a very mature IT company, btu this divide in application support vs. application development seems to work &#8220;OK&#8221;. Some times we march to the same beat, and other times we do not.</p>
<p>Your thoughts?</p>
<p>Dave</p>
]]></content:encoded>
	</item>
</channel>
</rss>

