<?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: User Stories Are Not Requirements	</title>
	<atom:link href="https://www.scrumexpert.com/knowledge/user-stories-are-not-requirements/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.scrumexpert.com/knowledge/user-stories-are-not-requirements/</link>
	<description></description>
	<lastBuildDate>Mon, 20 Jun 2016 15:20:33 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: raphael faudou		</title>
		<link>https://www.scrumexpert.com/knowledge/user-stories-are-not-requirements/#comment-27908</link>

		<dc:creator><![CDATA[raphael faudou]]></dc:creator>
		<pubDate>Fri, 27 May 2016 13:47:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.scrumexpert.com/?p=3451#comment-27908</guid>

					<description><![CDATA[One key point to get in mind is that user stories reflect expectations about target system (problem space) while system requirements reflect the engagement of system supplier about future system (solution space). That is clearly different in terms of goal.]]></description>
			<content:encoded><![CDATA[<p>One key point to get in mind is that user stories reflect expectations about target system (problem space) while system requirements reflect the engagement of system supplier about future system (solution space). That is clearly different in terms of goal.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
