<?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 failure rate still high. Agile is the answer.</title>
	<atom:link href="http://www.whitewallweb.com/blog/2009/03/23/project-failure-rate-still-high-agile-is-the-answer/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.whitewallweb.com/blog/2009/03/23/project-failure-rate-still-high-agile-is-the-answer/</link>
	<description></description>
	<lastBuildDate>Mon, 08 Nov 2010 13:39:32 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
	<item>
		<title>By: Noel</title>
		<link>http://www.whitewallweb.com/blog/2009/03/23/project-failure-rate-still-high-agile-is-the-answer/#comment-123</link>
		<dc:creator>Noel</dc:creator>
		<pubDate>Mon, 23 Mar 2009 11:59:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.whitewallweb.com/2009/03/23/project-failure-rate-still-high-agile-is-the-answer/#comment-123</guid>
		<description>While we&#039;re talking about value, members on any team need to be producing value - real value - for one another. Too often, non-agile approaches allow things to &#039;slip&#039; with shoddy work produced on the assumption that another role will be there to step in and &#039;test&#039; or &#039;quality control&#039; or &#039;architect&#039;.

The recommended interaction within scrum ensures more talking takes place, which becomes more exposure for work done poorly, and which leads to greater incentive/pressure to deliver high-value work, done right and responsibly. The result: more wins, more often.</description>
		<content:encoded><![CDATA[<p>While we&#8217;re talking about value, members on any team need to be producing value &#8211; real value &#8211; for one another. Too often, non-agile approaches allow things to &#8216;slip&#8217; with shoddy work produced on the assumption that another role will be there to step in and &#8216;test&#8217; or &#8216;quality control&#8217; or &#8216;architect&#8217;.</p>
<p>The recommended interaction within scrum ensures more talking takes place, which becomes more exposure for work done poorly, and which leads to greater incentive/pressure to deliver high-value work, done right and responsibly. The result: more wins, more often.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew</title>
		<link>http://www.whitewallweb.com/blog/2009/03/23/project-failure-rate-still-high-agile-is-the-answer/#comment-122</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Mon, 23 Mar 2009 11:10:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.whitewallweb.com/2009/03/23/project-failure-rate-still-high-agile-is-the-answer/#comment-122</guid>
		<description>Couldn&#039;t agree more - SCRUM and agile methodologies are the way forward...the waterfall SDLC is a thing of the past.

Important to note that SCRUM and agile methodolgies still follow all the project management principles (PMBOK) it&#039;s just the implementation cycle that is different...</description>
		<content:encoded><![CDATA[<p>Couldn&#8217;t agree more &#8211; SCRUM and agile methodologies are the way forward&#8230;the waterfall SDLC is a thing of the past.</p>
<p>Important to note that SCRUM and agile methodolgies still follow all the project management principles (PMBOK) it&#8217;s just the implementation cycle that is different&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

