<?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: 5 ERP Failure Stories and How to Avoid Becoming One	</title>
	<atom:link href="https://datixinc.com/blog/erp-failure-stories/feed/" rel="self" type="application/rss+xml" />
	<link>https://datixinc.com/blog/erp-failure-stories/</link>
	<description>Technology Solutions Delivered</description>
	<lastBuildDate>Mon, 30 Oct 2023 17:01:57 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.7.4</generator>
	<item>
		<title>
		By: Now What? How To Beat The ERP Post Go-Live Blues		</title>
		<link>https://datixinc.com/blog/erp-failure-stories/comment-page-1/#comment-3389</link>

		<dc:creator><![CDATA[Now What? How To Beat The ERP Post Go-Live Blues]]></dc:creator>
		<pubDate>Fri, 26 Feb 2016 22:40:06 +0000</pubDate>
		<guid isPermaLink="false">http://52.237.166.148/?p=8860#comment-3389</guid>

					<description><![CDATA[[&#8230;] day on the horizon and then figure it out from there? That line of thinking is a surefire way to invite failure into your ERP instance; that well known quote about ‘failure to plan’ comes to mind. The ERP [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] day on the horizon and then figure it out from there? That line of thinking is a surefire way to invite failure into your ERP instance; that well known quote about ‘failure to plan’ comes to mind. The ERP [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Managing Scope Creep in Your Implementation		</title>
		<link>https://datixinc.com/blog/erp-failure-stories/comment-page-1/#comment-3292</link>

		<dc:creator><![CDATA[Managing Scope Creep in Your Implementation]]></dc:creator>
		<pubDate>Thu, 11 Feb 2016 22:20:36 +0000</pubDate>
		<guid isPermaLink="false">http://52.237.166.148/?p=8860#comment-3292</guid>

					<description><![CDATA[[&#8230;] These are not very encouraging statistics, especially to any business looking to get started on their own enterprise software journey. However, there are ways to help your organization beat the odds and eliminate the danger of scope creep from their ERP or CRM, and that&#8217;s what we&#8217;re here for. Obviously, project scope must be clearly defined upfront, preferably before you even begin selecting your ERP vendor. These specific, measurable and reasonable goals will allow you to pick the software that will best help you achieve them after all. Then, as changes to scope arise they must be documented and addressed throughout the life of a project. Don&#8217;t let employees slip by timelines or have executives believe that a certain number of billable hours are needed to complete a deliverable when really it is twice that time. To ensure scope is tracked and managed, an integral part of a successful implementation process is a required project management budget for every project, regardless of size, to take preventative measures early and often that minimize scope creep and keep your ERP out of the dreaded failure zone. [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] These are not very encouraging statistics, especially to any business looking to get started on their own enterprise software journey. However, there are ways to help your organization beat the odds and eliminate the danger of scope creep from their ERP or CRM, and that&#8217;s what we&#8217;re here for. Obviously, project scope must be clearly defined upfront, preferably before you even begin selecting your ERP vendor. These specific, measurable and reasonable goals will allow you to pick the software that will best help you achieve them after all. Then, as changes to scope arise they must be documented and addressed throughout the life of a project. Don&#8217;t let employees slip by timelines or have executives believe that a certain number of billable hours are needed to complete a deliverable when really it is twice that time. To ensure scope is tracked and managed, an integral part of a successful implementation process is a required project management budget for every project, regardless of size, to take preventative measures early and often that minimize scope creep and keep your ERP out of the dreaded failure zone. [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Do You Need Business Process Reengineering?		</title>
		<link>https://datixinc.com/blog/erp-failure-stories/comment-page-1/#comment-3278</link>

		<dc:creator><![CDATA[Do You Need Business Process Reengineering?]]></dc:creator>
		<pubDate>Tue, 09 Feb 2016 22:29:23 +0000</pubDate>
		<guid isPermaLink="false">http://52.237.166.148/?p=8860#comment-3278</guid>

					<description><![CDATA[[&#8230;] they are ignored until they become too big to handle. This kind of business process neglect often ends in disaster. The solution? Business process reengineering (BPR). BPR is a total examination and reworking of [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] they are ignored until they become too big to handle. This kind of business process neglect often ends in disaster. The solution? Business process reengineering (BPR). BPR is a total examination and reworking of [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: ERP Conference Room Pilot: Step One Towards Success		</title>
		<link>https://datixinc.com/blog/erp-failure-stories/comment-page-1/#comment-3239</link>

		<dc:creator><![CDATA[ERP Conference Room Pilot: Step One Towards Success]]></dc:creator>
		<pubDate>Thu, 04 Feb 2016 22:20:45 +0000</pubDate>
		<guid isPermaLink="false">http://52.237.166.148/?p=8860#comment-3239</guid>

					<description><![CDATA[[&#8230;] a plan towards making sure that the problems disappear by go-live. One of the biggest factors of catastrophic ERP failure is poor planning and a lack of safety nets for every possible scenario that could go wrong with [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] a plan towards making sure that the problems disappear by go-live. One of the biggest factors of catastrophic ERP failure is poor planning and a lack of safety nets for every possible scenario that could go wrong with [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: The 7 Key ERP Project Phases		</title>
		<link>https://datixinc.com/blog/erp-failure-stories/comment-page-1/#comment-2999</link>

		<dc:creator><![CDATA[The 7 Key ERP Project Phases]]></dc:creator>
		<pubDate>Tue, 05 Jan 2016 22:46:51 +0000</pubDate>
		<guid isPermaLink="false">http://52.237.166.148/?p=8860#comment-2999</guid>

					<description><![CDATA[[&#8230;] and budget bloated. And with some of the very well publicized failure stories that we detailed in our last blog post, it’s not too surprising that enterprise resource planning software has taken on this somewhat [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] and budget bloated. And with some of the very well publicized failure stories that we detailed in our last blog post, it’s not too surprising that enterprise resource planning software has taken on this somewhat [&#8230;]</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
