<?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: Making Agile Requirements Work-No. 2</title>
	<atom:link href="http://www.dennisstevens.com/2009/10/27/making-agile-requirements-work-no-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.dennisstevens.com/2009/10/27/making-agile-requirements-work-no-2/</link>
	<description>Enabling the Agile Enterprise</description>
	<lastBuildDate>Mon, 14 Nov 2011 14:15:27 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Dennis Stevens and Associates &#187; Blog Archive &#187; The Agile Bargains</title>
		<link>http://www.dennisstevens.com/2009/10/27/making-agile-requirements-work-no-2/comment-page-1/#comment-2716</link>
		<dc:creator>Dennis Stevens and Associates &#187; Blog Archive &#187; The Agile Bargains</dc:creator>
		<pubDate>Wed, 02 Dec 2009 15:47:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.dennisstevens.com/2009/11/03/making-agile-requirements-work-no-2/#comment-2716</guid>
		<description>[...] Establish a Shared Language [...]</description>
		<content:encoded><![CDATA[<p>[...] Establish a Shared Language [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dennis Stevens and Associates &#187; Blog Archive &#187; Making Agile Requirements Work-NO 5</title>
		<link>http://www.dennisstevens.com/2009/10/27/making-agile-requirements-work-no-2/comment-page-1/#comment-2650</link>
		<dc:creator>Dennis Stevens and Associates &#187; Blog Archive &#187; Making Agile Requirements Work-NO 5</dc:creator>
		<pubDate>Mon, 30 Nov 2009 19:10:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.dennisstevens.com/2009/11/03/making-agile-requirements-work-no-2/#comment-2650</guid>
		<description>[...] that the way that requirements are captured should express the purpose and outcome, they should establish a shared language that communicates context and intent, is should be a stable view of the problem, and it should [...]</description>
		<content:encoded><![CDATA[<p>[...] that the way that requirements are captured should express the purpose and outcome, they should establish a shared language that communicates context and intent, is should be a stable view of the problem, and it should [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dennis Stevens and Associates &#187; Blog Archive &#187; Making Agile Requirements Work-No 4</title>
		<link>http://www.dennisstevens.com/2009/10/27/making-agile-requirements-work-no-2/comment-page-1/#comment-2262</link>
		<dc:creator>Dennis Stevens and Associates &#187; Blog Archive &#187; Making Agile Requirements Work-No 4</dc:creator>
		<pubDate>Wed, 04 Nov 2009 13:15:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.dennisstevens.com/2009/11/03/making-agile-requirements-work-no-2/#comment-2262</guid>
		<description>[...] have proposed that Agile Requirements must be built at a purpose and outcome level, must leverage shared language that communicates context and intent, and must be based on a stable view of the domain. But even with these in place requirements can [...]</description>
		<content:encoded><![CDATA[<p>[...] have proposed that Agile Requirements must be built at a purpose and outcome level, must leverage shared language that communicates context and intent, and must be based on a stable view of the domain. But even with these in place requirements can [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

