<?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"
	>
<channel>
	<title>Comments on: Outcomes over Features - the fifth agile value?</title>
	<atom:link href="http://dannorth.net/2006/10/outcomes-over-features-the-fifth-agile-value/feed" rel="self" type="application/rss+xml" />
	<link>http://dannorth.net/2006/10/outcomes-over-features-the-fifth-agile-value</link>
	<description>It's all behaviour</description>
	<pubDate>Sat, 11 Oct 2008 19:12:53 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Product Testing</title>
		<link>http://dannorth.net/2006/10/outcomes-over-features-the-fifth-agile-value#comment-8803</link>
		<dc:creator>Product Testing</dc:creator>
		<pubDate>Mon, 04 Feb 2008 04:59:57 +0000</pubDate>
		<guid isPermaLink="false">http://dannorth.net/archives/32#comment-8803</guid>
		<description>Role of QA and Testing in Software Product Development...

With the ever-shortening software release cycles, assuring the quality of codes, while managing the cost and risks involved, is a major challenge faced by a majority of software development enterprises nowadays. With project life cycles decreasing even...</description>
		<content:encoded><![CDATA[<p>Role of QA and Testing in Software Product Development&#8230;</p>
<p>With the ever-shortening software release cycles, assuring the quality of codes, while managing the cost and risks involved, is a major challenge faced by a majority of software development enterprises nowadays. With project life cycles decreasing even&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Manifesto for Agile Software Development (Agile Manifesto) &#171; PROJEKTMANAGEMENT BLOG</title>
		<link>http://dannorth.net/2006/10/outcomes-over-features-the-fifth-agile-value#comment-6241</link>
		<dc:creator>Manifesto for Agile Software Development (Agile Manifesto) &#171; PROJEKTMANAGEMENT BLOG</dc:creator>
		<pubDate>Tue, 16 Oct 2007 18:24:44 +0000</pubDate>
		<guid isPermaLink="false">http://dannorth.net/archives/32#comment-6241</guid>
		<description>[...] Outcomes over Features - the fifth agile value? [...]</description>
		<content:encoded><![CDATA[<p>[...] Outcomes over Features &#8211; the fifth agile value? [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan Hoegg</title>
		<link>http://dannorth.net/2006/10/outcomes-over-features-the-fifth-agile-value#comment-4772</link>
		<dc:creator>Ryan Hoegg</dc:creator>
		<pubDate>Wed, 21 Feb 2007 21:26:06 +0000</pubDate>
		<guid isPermaLink="false">http://dannorth.net/archives/32#comment-4772</guid>
		<description>Good insight, but I think this is really a corollary of "customer collaboration over contract negotiation".  If the product owner is resisting changes to the release plan based on new information, perhaps he views the release plan as a contract you've committed to.</description>
		<content:encoded><![CDATA[<p>Good insight, but I think this is really a corollary of &#8220;customer collaboration over contract negotiation&#8221;.  If the product owner is resisting changes to the release plan based on new information, perhaps he views the release plan as a contract you&#8217;ve committed to.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan Hoegg</title>
		<link>http://dannorth.net/2006/10/outcomes-over-features-the-fifth-agile-value#comment-4771</link>
		<dc:creator>Ryan Hoegg</dc:creator>
		<pubDate>Wed, 21 Feb 2007 21:22:29 +0000</pubDate>
		<guid isPermaLink="false">http://dannorth.net/archives/32#comment-4771</guid>
		<description>Good insight, but I think this is really a corollary of "Customer collaboration over contract negotiation".  Perhaps the commitment to a list of features is really a symptom of the product owner's unspoken assumption that the release plan is a contract?</description>
		<content:encoded><![CDATA[<p>Good insight, but I think this is really a corollary of &#8220;Customer collaboration over contract negotiation&#8221;.  Perhaps the commitment to a list of features is really a symptom of the product owner&#8217;s unspoken assumption that the release plan is a contract?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Community Blogs</title>
		<link>http://dannorth.net/2006/10/outcomes-over-features-the-fifth-agile-value#comment-3824</link>
		<dc:creator>Community Blogs</dc:creator>
		<pubDate>Sun, 21 Jan 2007 17:30:28 +0000</pubDate>
		<guid isPermaLink="false">http://dannorth.net/archives/32#comment-3824</guid>
		<description>Software Architecture Workshop in Arosa: back to reality...

Last week I had the privilege to spend 5 days in Arosa, Switzerland, among a group of people who were...</description>
		<content:encoded><![CDATA[<p>Software Architecture Workshop in Arosa: back to reality&#8230;</p>
<p>Last week I had the privilege to spend 5 days in Arosa, Switzerland, among a group of people who were&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
