<?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: Writing Good User Stories</title>
	<atom:link href="http://www.allaboutagile.com/writing-good-user-stories/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.allaboutagile.com/writing-good-user-stories/</link>
	<description>Agile Development Made Easy!</description>
	<lastBuildDate>Sun, 16 Jun 2013 21:01:11 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Sena</title>
		<link>http://www.allaboutagile.com/writing-good-user-stories/#comment-14986</link>
		<dc:creator>Sena</dc:creator>
		<pubDate>Tue, 18 Oct 2011 22:25:40 +0000</pubDate>
		<guid isPermaLink="false">http://allaboutagile.com/uncategorized/writing-good-user-stories/#comment-14986</guid>
		<description><![CDATA[Hi Kelly,

Could you also give a similar example of writing a non functional requirements please? This will help us to understand how to write user stories for such as well.

Thank you very much.
Sena]]></description>
		<content:encoded><![CDATA[<p>Hi Kelly,</p>
<p>Could you also give a similar example of writing a non functional requirements please? This will help us to understand how to write user stories for such as well.</p>
<p>Thank you very much.<br />
Sena</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bhavtosh</title>
		<link>http://www.allaboutagile.com/writing-good-user-stories/#comment-591</link>
		<dc:creator>Bhavtosh</dc:creator>
		<pubDate>Thu, 03 Sep 2009 08:21:19 +0000</pubDate>
		<guid isPermaLink="false">http://allaboutagile.com/uncategorized/writing-good-user-stories/#comment-591</guid>
		<description><![CDATA[very nice article&lt;br /&gt;&lt;br /&gt;,&lt;br /&gt;bhavtosh]]></description>
		<content:encoded><![CDATA[<p>very nice article</p>
<p>,<br />bhavtosh</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rajeev</title>
		<link>http://www.allaboutagile.com/writing-good-user-stories/#comment-513</link>
		<dc:creator>Rajeev</dc:creator>
		<pubDate>Wed, 22 Apr 2009 20:16:00 +0000</pubDate>
		<guid isPermaLink="false">http://allaboutagile.com/uncategorized/writing-good-user-stories/#comment-513</guid>
		<description><![CDATA[Kelly,&lt;br /&gt;&lt;br /&gt;Very useful and well written. It helped me come up to speed with Agile, a lot of PMs will find this a good starting point.&lt;br /&gt;&lt;br /&gt;Best,&lt;br /&gt;Rajeev]]></description>
		<content:encoded><![CDATA[<p>Kelly,</p>
<p>Very useful and well written. It helped me come up to speed with Agile, a lot of PMs will find this a good starting point.</p>
<p>Best,<br />Rajeev</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Unpublished Guy</title>
		<link>http://www.allaboutagile.com/writing-good-user-stories/#comment-509</link>
		<dc:creator>Unpublished Guy</dc:creator>
		<pubDate>Sat, 18 Apr 2009 17:17:00 +0000</pubDate>
		<guid isPermaLink="false">http://allaboutagile.com/uncategorized/writing-good-user-stories/#comment-509</guid>
		<description><![CDATA[This article reminded me about one user story that was once presented to me as an example. In this case the user were prospects at a trade show that would need a demonstration of a hypothetical company&#039;s yet-to-be-completed software product. So given a limited time to include the features of the product in a demo, what do you include. &lt;br /&gt;&lt;br /&gt;Almost everyone thought that a login would be necessary, which seems like a logical starting point. However, for the purposes of a demo, it really isn&#039;t that necessary. It is not exactly a feature you want to show off. Much better to focus on features that will impress and bypass the login.]]></description>
		<content:encoded><![CDATA[<p>This article reminded me about one user story that was once presented to me as an example. In this case the user were prospects at a trade show that would need a demonstration of a hypothetical company&#8217;s yet-to-be-completed software product. So given a limited time to include the features of the product in a demo, what do you include. </p>
<p>Almost everyone thought that a login would be necessary, which seems like a logical starting point. However, for the purposes of a demo, it really isn&#8217;t that necessary. It is not exactly a feature you want to show off. Much better to focus on features that will impress and bypass the login.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrick Merg</title>
		<link>http://www.allaboutagile.com/writing-good-user-stories/#comment-428</link>
		<dc:creator>Patrick Merg</dc:creator>
		<pubDate>Sat, 07 Feb 2009 15:12:00 +0000</pubDate>
		<guid isPermaLink="false">http://allaboutagile.com/uncategorized/writing-good-user-stories/#comment-428</guid>
		<description><![CDATA[Hello&lt;br/&gt; Nice set of articles.  I read the comments on making user stories Independent. Making a user story Independent is really hard especially on large projects.   &lt;br/&gt;Pat]]></description>
		<content:encoded><![CDATA[<p>Hello<br /> Nice set of articles.  I read the comments on making user stories Independent. Making a user story Independent is really hard especially on large projects.   <br />Pat</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PierG</title>
		<link>http://www.allaboutagile.com/writing-good-user-stories/#comment-262</link>
		<dc:creator>PierG</dc:creator>
		<pubDate>Fri, 11 Apr 2008 11:30:00 +0000</pubDate>
		<guid isPermaLink="false">http://allaboutagile.com/uncategorized/writing-good-user-stories/#comment-262</guid>
		<description><![CDATA[Kelly,&lt;br/&gt;congrats, a very good summary.&lt;br/&gt;PierG&lt;br/&gt;http://pierg.wordpress.com]]></description>
		<content:encoded><![CDATA[<p>Kelly,<br />congrats, a very good summary.<br />PierG<br /><a href="http://pierg.wordpress.com" rel="nofollow">http://pierg.wordpress.com</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- Quick Cache: failed to write cache. The cache/ directory is either non-existent ( and could not be created ) or it is not writable. -->