<?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: Welcome to the SAP Project Management &amp; Project Observations Blog</title>
	<atom:link href="http://www.dataxstream.com/2009/10/sap-project-management-blog/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.dataxstream.com/2009/10/sap-project-management-blog/</link>
	<description>SAP Certified Consultants</description>
	<lastBuildDate>Mon, 06 Feb 2012 03:05:34 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Derek Vansant</title>
		<link>http://www.dataxstream.com/2009/10/sap-project-management-blog/comment-page-1/#comment-462</link>
		<dc:creator>Derek Vansant</dc:creator>
		<pubDate>Thu, 01 Oct 2009 19:11:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.dataxstream.com/?p=2496#comment-462</guid>
		<description>Hi, Tim. I would be interested in learning more about how most enterprise software implementation projects are managed.  In particular, how are requirements, tests, defects, change requests and issues documented and tracked. 

If, in your experience, most projects have been managed with emails, Word docs, and spreadsheets, I&#039;d love to know why more specialized tools were not chosen. Are emails, Word docs, and spreadsheets sufficient? Are they chosen for cost reasons? Are they used because that&#039;s what people already have access to? Other reasons?

I&#039;ve asked this question of several people, but haven&#039;t yet reached any consensus on the issue and would love your insight.</description>
		<content:encoded><![CDATA[<p>Hi, Tim. I would be interested in learning more about how most enterprise software implementation projects are managed.  In particular, how are requirements, tests, defects, change requests and issues documented and tracked. </p>
<p>If, in your experience, most projects have been managed with emails, Word docs, and spreadsheets, I&#8217;d love to know why more specialized tools were not chosen. Are emails, Word docs, and spreadsheets sufficient? Are they chosen for cost reasons? Are they used because that&#8217;s what people already have access to? Other reasons?</p>
<p>I&#8217;ve asked this question of several people, but haven&#8217;t yet reached any consensus on the issue and would love your insight.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

