<?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: 4 Tips to Consider if you&#8217;re Thinking of Adopting an On Demand Strategy</title>
	<atom:link href="http://www.softwareindustryinsights.com/2009/08/4-tips-to-consider-if-youre-thinking-of-adopting-an-on-demand-strategy/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.softwareindustryinsights.com/2009/08/4-tips-to-consider-if-youre-thinking-of-adopting-an-on-demand-strategy/</link>
	<description>Insights into how technology and the outsourcing of R&#38;D are changing the software industry</description>
	<lastBuildDate>Fri, 30 Dec 2011 02:32:43 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ernie Huber</title>
		<link>http://www.softwareindustryinsights.com/2009/08/4-tips-to-consider-if-youre-thinking-of-adopting-an-on-demand-strategy/comment-page-1/#comment-3</link>
		<dc:creator>Ernie Huber</dc:creator>
		<pubDate>Wed, 26 Aug 2009 17:15:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.softwareindustryinsights.com/?p=31#comment-3</guid>
		<description>Great post Glenn
I can&#039;t emphasize enough your point about architectural tradeoffs and would like to also specifically call out the system integration considerations.  I have found that to be a challenge with every SaaS implementation.

Also, I would re-emphasize the organizational impact especially when it comes to support. Everyone, including the business, needs to understand that the majority of the support work shifts to the vendor.  So it is critical to get the SLAs air tight as you mentioned.

In the end I believe it is well worth the effort.  This model can work very well and allow IT resources to focus the majority of their time on value added projects rather than keeping the lights on.</description>
		<content:encoded><![CDATA[<p>Great post Glenn<br />
I can&#8217;t emphasize enough your point about architectural tradeoffs and would like to also specifically call out the system integration considerations.  I have found that to be a challenge with every SaaS implementation.</p>
<p>Also, I would re-emphasize the organizational impact especially when it comes to support. Everyone, including the business, needs to understand that the majority of the support work shifts to the vendor.  So it is critical to get the SLAs air tight as you mentioned.</p>
<p>In the end I believe it is well worth the effort.  This model can work very well and allow IT resources to focus the majority of their time on value added projects rather than keeping the lights on.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

