<?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: Project Team Roles: The Spots You Need to Fill	</title>
	<atom:link href="https://datixinc.com/blog/project-team-roles/feed/" rel="self" type="application/rss+xml" />
	<link>https://datixinc.com/blog/project-team-roles/</link>
	<description>Technology Solutions Delivered</description>
	<lastBuildDate>Wed, 13 Dec 2023 20:43:25 +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/project-team-roles/comment-page-1/#comment-3368</link>

		<dc:creator><![CDATA[Now What? How To Beat The ERP Post Go-Live Blues]]></dc:creator>
		<pubDate>Wed, 24 Feb 2016 22:51:12 +0000</pubDate>
		<guid isPermaLink="false">http://52.237.166.148/?p=7642#comment-3368</guid>

					<description><![CDATA[[&#8230;] employees abandon the software in droves or small, unnoticed errors blossom into fatal flaws. The smart ERP project team will have a solid plan in place for the ERP post go-live period, and how to keep that honeymoon [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] employees abandon the software in droves or small, unnoticed errors blossom into fatal flaws. The smart ERP project team will have a solid plan in place for the ERP post go-live period, and how to keep that honeymoon [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: ERP Reporting Strategy: The Critical Steps		</title>
		<link>https://datixinc.com/blog/project-team-roles/comment-page-1/#comment-3241</link>

		<dc:creator><![CDATA[ERP Reporting Strategy: The Critical Steps]]></dc:creator>
		<pubDate>Thu, 04 Feb 2016 22:21:58 +0000</pubDate>
		<guid isPermaLink="false">http://52.237.166.148/?p=7642#comment-3241</guid>

					<description><![CDATA[[&#8230;] magically create revenue and shave time off of every employee’s daily tasks. But come go-live, the project team finds that employees have been distracted by the hype, and no one has been properly trained in [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] magically create revenue and shave time off of every employee’s daily tasks. But come go-live, the project team finds that employees have been distracted by the hype, and no one has been properly trained in [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: ERP Conference Room Pilot: Step One Towards Success		</title>
		<link>https://datixinc.com/blog/project-team-roles/comment-page-1/#comment-3207</link>

		<dc:creator><![CDATA[ERP Conference Room Pilot: Step One Towards Success]]></dc:creator>
		<pubDate>Mon, 01 Feb 2016 22:44:43 +0000</pubDate>
		<guid isPermaLink="false">http://52.237.166.148/?p=7642#comment-3207</guid>

					<description><![CDATA[[&#8230;] and team members across departments interact with the software early on will not only help your project team to understand areas of the software that will need work, it also acts as an early training and [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] and team members across departments interact with the software early on will not only help your project team to understand areas of the software that will need work, it also acts as an early training and [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: The ERP System Implementation Hype Sequence &#124; Datix		</title>
		<link>https://datixinc.com/blog/project-team-roles/comment-page-1/#comment-2953</link>

		<dc:creator><![CDATA[The ERP System Implementation Hype Sequence &#124; Datix]]></dc:creator>
		<pubDate>Tue, 29 Dec 2015 19:00:42 +0000</pubDate>
		<guid isPermaLink="false">http://52.237.166.148/?p=7642#comment-2953</guid>

					<description><![CDATA[[&#8230;] like? We&#8217;ve covered the importance of roles within a project team before, and even covered who should be on a project team. This is critical to ensuring your organization has the right bandwidth to complete the project [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] like? We&#8217;ve covered the importance of roles within a project team before, and even covered who should be on a project team. This is critical to ensuring your organization has the right bandwidth to complete the project [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: How Long Does An ERP Implementation Take? — Q &#38; A		</title>
		<link>https://datixinc.com/blog/project-team-roles/comment-page-1/#comment-2944</link>

		<dc:creator><![CDATA[How Long Does An ERP Implementation Take? — Q &#38; A]]></dc:creator>
		<pubDate>Tue, 29 Dec 2015 18:56:47 +0000</pubDate>
		<guid isPermaLink="false">http://52.237.166.148/?p=7642#comment-2944</guid>

					<description><![CDATA[[&#8230;] The team performing the implementation should be the go to expert for scheduling the project. Sometimes the client has business reasons for completing the project by a specified date. For those cases, the implementation partner should have an idea of what work could be done by that point. Those conversations will determine which goals are a priority and which are secondary. These changes should take the upmost consideration, as they often modify the scope of the project. If improperly communicated, the client may fail to understand why the project isn’t fully completed on the date it was intended. Users will also lose interest in the system, because there will be no communication to them as to when they should expect their portion to up and running. You can read more about project roles here. [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] The team performing the implementation should be the go to expert for scheduling the project. Sometimes the client has business reasons for completing the project by a specified date. For those cases, the implementation partner should have an idea of what work could be done by that point. Those conversations will determine which goals are a priority and which are secondary. These changes should take the upmost consideration, as they often modify the scope of the project. If improperly communicated, the client may fail to understand why the project isn’t fully completed on the date it was intended. Users will also lose interest in the system, because there will be no communication to them as to when they should expect their portion to up and running. You can read more about project roles here. [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Salesforce Best Practices &#124; 5 Ways To Improve CRM Use		</title>
		<link>https://datixinc.com/blog/project-team-roles/comment-page-1/#comment-1636</link>

		<dc:creator><![CDATA[Salesforce Best Practices &#124; 5 Ways To Improve CRM Use]]></dc:creator>
		<pubDate>Thu, 02 Jul 2015 14:53:58 +0000</pubDate>
		<guid isPermaLink="false">http://52.237.166.148/?p=7642#comment-1636</guid>

					<description><![CDATA[[&#8230;] implementation and adoption is solely tied to how well the system is configured, and how well the project team aligns the business processes to the technical setup of the system. This caution is well warranted, but not overly difficult to [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] implementation and adoption is solely tied to how well the system is configured, and how well the project team aligns the business processes to the technical setup of the system. This caution is well warranted, but not overly difficult to [&#8230;]</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
