<?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>Michael Cross - Microsoft Dynamics CRM Consultant &#187; Project Management</title>
	<atom:link href="http://michaelcrossconsultant.com/category/project-management/feed/" rel="self" type="application/rss+xml" />
	<link>http://michaelcrossconsultant.com</link>
	<description>Using Microsoft Dynamics CRM to improve your relationships with customers and increase your sales and profits.</description>
	<lastBuildDate>Fri, 20 Jan 2012 06:51:59 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Managing Risk in a CRM Implementation</title>
		<link>http://michaelcrossconsultant.com/2007/06/26/managing-risk-in-a-crm-implementation/</link>
		<comments>http://michaelcrossconsultant.com/2007/06/26/managing-risk-in-a-crm-implementation/#comments</comments>
		<pubDate>Tue, 26 Jun 2007 04:08:57 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Project Management]]></category>

		<guid isPermaLink="false">http://michaelcrossconsultant.com/2007/06/26/managing-risk-in-a-crm-implementation/</guid>
		<description><![CDATA[In every Microsoft CRM implementation I have been involved in, there has been at least one item that I considered to be a risk (no surprises there). The most common risk factors I&#8217;ve come across are: Availability of qualified resources Complexity of technical infrastructure and ensuring everything works Complexity of functional requirements and impact on [...]]]></description>
			<content:encoded><![CDATA[<p>In every Microsoft CRM implementation I have been involved in, there has been at least one item that I considered to be a risk (no surprises there).</p>
<p>The most common risk factors I&#8217;ve come across are:</p>
<ul>
<li>Availability of qualified resources</li>
<li>Complexity of technical infrastructure and ensuring everything works</li>
<li>Complexity of functional requirements and impact on customizations, particularly custom programming</li>
<li>Third-party add-ons and utilities</li>
<li>Data migration</li>
<li>Systems integration</li>
</ul>
<p>In the last project, two items ended up causing trouble.</p>
<p>The first was a third-party add-on that could not be installed correctly, or did not work 100% when it was installed. It took over two weeks and many hours of remote support sessions with the vendor, plus a patch to fix a bug, before it was working as expected.</p>
<p>The second was the technical infrastructure, particularly getting the outgoing e-mail to actually go out (solved by changing the SMTP settings), and getting the incoming e-mail to appear as activities in CRM (still a work in progress).</p>
<p>The lesson I learned? Identify as early as possible the risk factors and figure out how to mitigate those risks.</p>
<p>For example, don&#8217;t wait until the week before go live to install third-party add-ons, especially complex ones. Or if you think there is going to be a need for custom programming, then line up a programmer so they are ready when you need them.</p>
<p>Bottom line: Don&#8217;t sugarcoat the situation, and don&#8217;t make assumptions. Get into the details early and often, and you&#8217;ll be okay.</p>
]]></content:encoded>
			<wfw:commentRss>http://michaelcrossconsultant.com/2007/06/26/managing-risk-in-a-crm-implementation/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

