<?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: CRM Project Plans &#8211; Where Does It All Go Wrong?</title>
	<atom:link href="http://crmweblog.crmmastery.com/2010/01/crm-project-plans-where-does-it-all-go-wrong/feed/" rel="self" type="application/rss+xml" />
	<link>http://crmweblog.crmmastery.com/2010/01/crm-project-plans-where-does-it-all-go-wrong/</link>
	<description>CRM Best Practice and Industry News</description>
	<lastBuildDate>Tue, 01 Feb 2011 09:22:50 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Intelestream Inc</title>
		<link>http://crmweblog.crmmastery.com/2010/01/crm-project-plans-where-does-it-all-go-wrong/comment-page-1/#comment-6623</link>
		<dc:creator>Intelestream Inc</dc:creator>
		<pubDate>Mon, 14 Jun 2010 22:52:35 +0000</pubDate>
		<guid isPermaLink="false">http://crmweblog.crmmastery.com/?p=1906#comment-6623</guid>
		<description>At Intelestream we have written a whitepaper containing important considerations when planning a CRM project. It can be read at our web page.</description>
		<content:encoded><![CDATA[<p>At Intelestream we have written a whitepaper containing important considerations when planning a CRM project. It can be read at our web page.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arturo F Munoz</title>
		<link>http://crmweblog.crmmastery.com/2010/01/crm-project-plans-where-does-it-all-go-wrong/comment-page-1/#comment-6270</link>
		<dc:creator>Arturo F Munoz</dc:creator>
		<pubDate>Tue, 23 Mar 2010 02:36:07 +0000</pubDate>
		<guid isPermaLink="false">http://crmweblog.crmmastery.com/?p=1906#comment-6270</guid>
		<description>I think system design should be split into design vs. fit, because with SaaS vs. on-premise solutions you&#039;re not designing a system but determining instead how well the existing model provided by the SaaS might match the process demands that your organization has envisioned.

With a SaaS you get rapid deployment but you trade off customization flexibility, and working through those trade-offs can take time.</description>
		<content:encoded><![CDATA[<p>I think system design should be split into design vs. fit, because with SaaS vs. on-premise solutions you&#8217;re not designing a system but determining instead how well the existing model provided by the SaaS might match the process demands that your organization has envisioned.</p>
<p>With a SaaS you get rapid deployment but you trade off customization flexibility, and working through those trade-offs can take time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MarenKate</title>
		<link>http://crmweblog.crmmastery.com/2010/01/crm-project-plans-where-does-it-all-go-wrong/comment-page-1/#comment-6146</link>
		<dc:creator>MarenKate</dc:creator>
		<pubDate>Fri, 29 Jan 2010 09:42:43 +0000</pubDate>
		<guid isPermaLink="false">http://crmweblog.crmmastery.com/?p=1906#comment-6146</guid>
		<description>Thanks for the points. I have a team and i think i&#039;ll be needing this kind of informations to make them effective.</description>
		<content:encoded><![CDATA[<p>Thanks for the points. I have a team and i think i&#8217;ll be needing this kind of informations to make them effective.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

