<?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: When IT projects go bad</title>
	<atom:link href="http://www.techcentral.co.za/when-it-projects-go-bad/13044/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.techcentral.co.za/when-it-projects-go-bad/13044/</link>
	<description>South Africa&#039;s technology news leader</description>
	<lastBuildDate>Tue, 22 May 2012 09:19:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Ronaldo</title>
		<link>http://www.techcentral.co.za/when-it-projects-go-bad/13044/comment-page-1/#comment-3944</link>
		<dc:creator>Ronaldo</dc:creator>
		<pubDate>Mon, 01 Mar 2010 08:21:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcentral.co.za/?p=13044#comment-3944</guid>
		<description>I think that it is important to emphasize that generally speaking the client has a role to play in both the success and failure of any given IT project. Seldom is a project outsourced entire to a contracting partner where all responsibility is handed over and thus were all accountability will reside. 

Therefore as most projects involve a number of responsible parties including the client, success form a contractual and project management perspective, rests in the ability to clearly separate roles and responsibilities and manage these on an ongoing basis throughout the project life time.

A vendor or contractor is often dependent on the client for its own deliveries, and its failure to deliver can often be pointed right back at the client.</description>
		<content:encoded><![CDATA[<p>I think that it is important to emphasize that generally speaking the client has a role to play in both the success and failure of any given IT project. Seldom is a project outsourced entire to a contracting partner where all responsibility is handed over and thus were all accountability will reside. </p>
<p>Therefore as most projects involve a number of responsible parties including the client, success form a contractual and project management perspective, rests in the ability to clearly separate roles and responsibilities and manage these on an ongoing basis throughout the project life time.</p>
<p>A vendor or contractor is often dependent on the client for its own deliveries, and its failure to deliver can often be pointed right back at the client.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Piet Pompies</title>
		<link>http://www.techcentral.co.za/when-it-projects-go-bad/13044/comment-page-1/#comment-3719</link>
		<dc:creator>Piet Pompies</dc:creator>
		<pubDate>Wed, 24 Feb 2010 07:12:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.techcentral.co.za/?p=13044#comment-3719</guid>
		<description>I think that it is important to distinguish between software development and IT Systems. Software development is an inherently risky, human skill dependent activity whereas IT systems rely on product choice and best practice configuration for success.

It is unlikely that corporates can hire and maintain the skills required for excellent software development and documentation and access to source code do not manage risk in any significant way.

Implementation of systems from most of the large IT hardware and software systems will enjoy support and access to best practice experiences. This just means smart buying and sufficient budget.

The risk inherent in software development can be partly mitigated by choosing the optimal process. Think waterfall vs agile approaches. However the only real way of avoiding the disaster is hiring the smarts and experience of veteran, professional software developers (not just analysts and managers). In my (humble) experience these are in vast short supply.</description>
		<content:encoded><![CDATA[<p>I think that it is important to distinguish between software development and IT Systems. Software development is an inherently risky, human skill dependent activity whereas IT systems rely on product choice and best practice configuration for success.</p>
<p>It is unlikely that corporates can hire and maintain the skills required for excellent software development and documentation and access to source code do not manage risk in any significant way.</p>
<p>Implementation of systems from most of the large IT hardware and software systems will enjoy support and access to best practice experiences. This just means smart buying and sufficient budget.</p>
<p>The risk inherent in software development can be partly mitigated by choosing the optimal process. Think waterfall vs agile approaches. However the only real way of avoiding the disaster is hiring the smarts and experience of veteran, professional software developers (not just analysts and managers). In my (humble) experience these are in vast short supply.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

