<?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: Holistic vs. Dogmatic Agile Definition &#8211; Results Matter!</title>
	<atom:link href="http://www.agileforall.com/2009/02/13/holistic-vs-dogmatic-agile-definition-results-matter/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.agileforall.com/2009/02/13/holistic-vs-dogmatic-agile-definition-results-matter/</link>
	<description>Agile For All</description>
	<lastBuildDate>Fri, 13 Jan 2012 18:11:43 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Cameron Wolff</title>
		<link>http://www.agileforall.com/2009/02/13/holistic-vs-dogmatic-agile-definition-results-matter/comment-page-1/#comment-162</link>
		<dc:creator>Cameron Wolff</dc:creator>
		<pubDate>Tue, 21 Apr 2009 12:51:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.agileforall.com/blog/?p=90#comment-162</guid>
		<description>I would modify the definition to read:

Disciplined Agile is:
An iterative and incremental (evolutionary) approach to software development
which is performed in a highly collaborative manner
by self-organizing teams within an effective governance framework
with “just enough” ceremony
and engineering practices to sustain the
the production of high quality software
in a cost effective and timely manner
 which meets the changing needs of its stakeholders.</description>
		<content:encoded><![CDATA[<p>I would modify the definition to read:</p>
<p>Disciplined Agile is:<br />
An iterative and incremental (evolutionary) approach to software development<br />
which is performed in a highly collaborative manner<br />
by self-organizing teams within an effective governance framework<br />
with “just enough” ceremony<br />
and engineering practices to sustain the<br />
the production of high quality software<br />
in a cost effective and timely manner<br />
 which meets the changing needs of its stakeholders.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Making Agile a Reality for All</title>
		<link>http://www.agileforall.com/2009/02/13/holistic-vs-dogmatic-agile-definition-results-matter/comment-page-1/#comment-112</link>
		<dc:creator>Making Agile a Reality for All</dc:creator>
		<pubDate>Tue, 07 Apr 2009 16:37:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.agileforall.com/blog/?p=90#comment-112</guid>
		<description>[...] Trust would slowly return.  Today consumers and companies that purchase software don&#8217;t trust the manufacturers.  Why?  Because they don&#8217;t deliver high value software.  They don&#8217;t deliver with high quality.  And they don&#8217;t do it quickly.  At least most don&#8217;t do those three things.  Those that do are phenomenally successful.  Let&#8217;s make more companies successful by doing the same thing.  Oh yeah, by the way, those three things form my definition of agile. [...]</description>
		<content:encoded><![CDATA[<p>[...] Trust would slowly return.  Today consumers and companies that purchase software don&#8217;t trust the manufacturers.  Why?  Because they don&#8217;t deliver high value software.  They don&#8217;t deliver with high quality.  And they don&#8217;t do it quickly.  At least most don&#8217;t do those three things.  Those that do are phenomenally successful.  Let&#8217;s make more companies successful by doing the same thing.  Oh yeah, by the way, those three things form my definition of agile. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

