<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Defining &#8216;Agile Software Development&#8217; on Wikipedia</title>
	<atom:link href="http://agileelements.wordpress.com/2008/07/29/defining-agile-software-development-on-wikipedia/feed/" rel="self" type="application/rss+xml" />
	<link>http://agileelements.wordpress.com/2008/07/29/defining-agile-software-development-on-wikipedia/</link>
	<description></description>
	<lastBuildDate>Thu, 12 Nov 2009 19:25:30 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Agile Development on Wikipedia &#171; Agile Elements</title>
		<link>http://agileelements.wordpress.com/2008/07/29/defining-agile-software-development-on-wikipedia/#comment-172</link>
		<dc:creator>Agile Development on Wikipedia &#171; Agile Elements</dc:creator>
		<pubDate>Mon, 29 Sep 2008 21:46:52 +0000</pubDate>
		<guid isPermaLink="false">http://agileelements.wordpress.com/?p=109#comment-172</guid>
		<description>[...] Defining &#8216;Agile Software Development&#8217; on&#160;Wikipedia  [...]</description>
		<content:encoded><![CDATA[<p>[...] Defining &#8216;Agile Software Development&#8217; on&nbsp;Wikipedia  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Defining Agile Development (part 2) &#171; Agile Elements</title>
		<link>http://agileelements.wordpress.com/2008/07/29/defining-agile-software-development-on-wikipedia/#comment-120</link>
		<dc:creator>Defining Agile Development (part 2) &#171; Agile Elements</dc:creator>
		<pubDate>Tue, 12 Aug 2008 10:49:22 +0000</pubDate>
		<guid isPermaLink="false">http://agileelements.wordpress.com/?p=109#comment-120</guid>
		<description>[...] Defining &#8216;Agile Software Development&#8217; on&#160;Wikipedia  [...]</description>
		<content:encoded><![CDATA[<p>[...] Defining &#8216;Agile Software Development&#8217; on&nbsp;Wikipedia  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin E. Schlabach</title>
		<link>http://agileelements.wordpress.com/2008/07/29/defining-agile-software-development-on-wikipedia/#comment-108</link>
		<dc:creator>Kevin E. Schlabach</dc:creator>
		<pubDate>Tue, 29 Jul 2008 16:49:46 +0000</pubDate>
		<guid isPermaLink="false">http://agileelements.wordpress.com/?p=109#comment-108</guid>
		<description>I can&#039;t take credit for this one, so I&#039;ll just point you to the source.

Mike Cottmeyer posted on March 18, 2008 a post that was distributed to several blogs... I really like his 3 points elevator speech as an overview.

http://blog.versionone.net/blog/2008/03/the-agile-eleva.html

excerpt: &quot;agile is basically three things: a set of engineering best practices that allow for rapid delivery of high-quality software, a project management process that encourages frequent inspection and adaptation, and a leadership philosophy that encourages team work and accountability.&quot;

I felt like this is a modern summary of the manifesto or principles found on the original site.

Good luck.</description>
		<content:encoded><![CDATA[<p>I can&#8217;t take credit for this one, so I&#8217;ll just point you to the source.</p>
<p>Mike Cottmeyer posted on March 18, 2008 a post that was distributed to several blogs&#8230; I really like his 3 points elevator speech as an overview.</p>
<p><a href="http://blog.versionone.net/blog/2008/03/the-agile-eleva.html" rel="nofollow">http://blog.versionone.net/blog/2008/03/the-agile-eleva.html</a></p>
<p>excerpt: &#8220;agile is basically three things: a set of engineering best practices that allow for rapid delivery of high-quality software, a project management process that encourages frequent inspection and adaptation, and a leadership philosophy that encourages team work and accountability.&#8221;</p>
<p>I felt like this is a modern summary of the manifesto or principles found on the original site.</p>
<p>Good luck.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AlexForbes</title>
		<link>http://agileelements.wordpress.com/2008/07/29/defining-agile-software-development-on-wikipedia/#comment-107</link>
		<dc:creator>AlexForbes</dc:creator>
		<pubDate>Tue, 29 Jul 2008 15:57:42 +0000</pubDate>
		<guid isPermaLink="false">http://agileelements.wordpress.com/?p=109#comment-107</guid>
		<description>What about the fact that each iteration delivers working software? That phases within each iteration are nearly concurrent? The elimination of waste? You could also separate the management from engineering practices for clarity (for e.g., self-directed teams or information radiators vs. pair programming or test-driven development).

I think Damon Poole, CTO, AccuRev would be a valuable source, but he&#039;s pretty busy speaking about Agile at tradeshows around the country these coming months. I&#039;ll mention it to him.

Good luck,
Alex</description>
		<content:encoded><![CDATA[<p>What about the fact that each iteration delivers working software? That phases within each iteration are nearly concurrent? The elimination of waste? You could also separate the management from engineering practices for clarity (for e.g., self-directed teams or information radiators vs. pair programming or test-driven development).</p>
<p>I think Damon Poole, CTO, AccuRev would be a valuable source, but he&#8217;s pretty busy speaking about Agile at tradeshows around the country these coming months. I&#8217;ll mention it to him.</p>
<p>Good luck,<br />
Alex</p>
]]></content:encoded>
	</item>
</channel>
</rss>
