<?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: Organizational Patterns of Agile Software Development</title>
	<atom:link href="http://www.wombatnation.com/2004/10/organizational-patterns-of-agile-software-development/feed" rel="self" type="application/rss+xml" />
	<link>http://www.wombatnation.com/2004/10/organizational-patterns-of-agile-software-development</link>
	<description>Speech Applications, Soccer, Hacking, Intellectual Property, and Incinerating Toilets</description>
	<lastBuildDate>Tue, 16 Mar 2010 01:26:36 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Robert</title>
		<link>http://www.wombatnation.com/2004/10/organizational-patterns-of-agile-software-development/comment-page-1#comment-111421</link>
		<dc:creator>Robert</dc:creator>
		<pubDate>Fri, 17 Apr 2009 15:16:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.wombatnation.com/2004/10/organizational-patterns-of-agile-software-development#comment-111421</guid>
		<description>Personal experience, mostly.

It&#039;s, of course, possible that the certification process at Avaya was badly mismanaged by the internal people and the external auditors. But, having read what was required to become certified, it looked like a design-by-committee-that-can&#039;t-say-no process. That is, the requirements seemed to be a huge list of every idea that a big group of people thought might be a good idea.</description>
		<content:encoded><![CDATA[<p>Personal experience, mostly.</p>
<p>It&#8217;s, of course, possible that the certification process at Avaya was badly mismanaged by the internal people and the external auditors. But, having read what was required to become certified, it looked like a design-by-committee-that-can&#8217;t-say-no process. That is, the requirements seemed to be a huge list of every idea that a big group of people thought might be a good idea.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anton</title>
		<link>http://www.wombatnation.com/2004/10/organizational-patterns-of-agile-software-development/comment-page-1#comment-111420</link>
		<dc:creator>Anton</dc:creator>
		<pubDate>Fri, 17 Apr 2009 09:44:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.wombatnation.com/2004/10/organizational-patterns-of-agile-software-development#comment-111420</guid>
		<description>&quot;Oh, and did I mention that I think ISO certification is a bad idea for software development organzations?&quot;

Why is do you think so? I think it will unify the work flow!</description>
		<content:encoded><![CDATA[<p>&#8220;Oh, and did I mention that I think ISO certification is a bad idea for software development organzations?&#8221;</p>
<p>Why is do you think so? I think it will unify the work flow!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
