<?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: What are user stories, and why should I use them?</title>
	<atom:link href="http://jonathanbabcock.com/2007/11/03/what-are-user-stories-and-why-should-i-use-them/feed" rel="self" type="application/rss+xml" />
	<link>http://jonathanbabcock.com/2007/11/03/what-are-user-stories-and-why-should-i-use-them/</link>
	<description>Business Analysis &#124; Software Methodology &#124; Process Improvement</description>
	<pubDate>Wed, 15 Oct 2008 23:06:11 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: JB</title>
		<link>http://jonathanbabcock.com/2007/11/03/what-are-user-stories-and-why-should-i-use-them/#comment-561</link>
		<dc:creator>JB</dc:creator>
		<pubDate>Mon, 21 Jan 2008 20:11:33 +0000</pubDate>
		<guid isPermaLink="false">http://jonathanbabcock.com/2007/11/03/what-are-user-stories-and-why-should-i-use-them/#comment-561</guid>
		<description>I appreciate the comment, Kevin - and I love the new IIBA blog. You guys are doing a great job.

I also got the impression that there isn't a great deal of difference - semantics aside - between the user story and the use case scenario. 

I'm admittedly more a student of agile methods than a practitioner. I've read the books,the articles and the blogs and have participated in a few quick projects that were termed "XP" or "rapid development", but have never worked extensively in what purists would consider an agile environment. I do have to agree that, regardless of the methodology, tossing documentation that represents important decisions and rules seems like risky business.</description>
		<content:encoded><![CDATA[<p>I appreciate the comment, Kevin - and I love the new IIBA blog. You guys are doing a great job.</p>
<p>I also got the impression that there isn&#8217;t a great deal of difference - semantics aside - between the user story and the use case scenario. </p>
<p>I&#8217;m admittedly more a student of agile methods than a practitioner. I&#8217;ve read the books,the articles and the blogs and have participated in a few quick projects that were termed &#8220;XP&#8221; or &#8220;rapid development&#8221;, but have never worked extensively in what purists would consider an agile environment. I do have to agree that, regardless of the methodology, tossing documentation that represents important decisions and rules seems like risky business.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Brennan</title>
		<link>http://jonathanbabcock.com/2007/11/03/what-are-user-stories-and-why-should-i-use-them/#comment-556</link>
		<dc:creator>Kevin Brennan</dc:creator>
		<pubDate>Sun, 20 Jan 2008 17:29:58 +0000</pubDate>
		<guid isPermaLink="false">http://jonathanbabcock.com/2007/11/03/what-are-user-stories-and-why-should-i-use-them/#comment-556</guid>
		<description>Except for the "torn up and thrown away" part, it seems to me that "scenario" (in use case terminology) and "user story" are pretty much identical.

As for the "torn up and thrown away" part--well, I have yet to find a place where this actually was OK in real life. Almost every Agile project I've encountered ended up requiring a major documentation effort after the project wound down and the business owners started to realize that the only people who knew how the system worked were leaving.</description>
		<content:encoded><![CDATA[<p>Except for the &#8220;torn up and thrown away&#8221; part, it seems to me that &#8220;scenario&#8221; (in use case terminology) and &#8220;user story&#8221; are pretty much identical.</p>
<p>As for the &#8220;torn up and thrown away&#8221; part&#8211;well, I have yet to find a place where this actually was OK in real life. Almost every Agile project I&#8217;ve encountered ended up requiring a major documentation effort after the project wound down and the business owners started to realize that the only people who knew how the system worked were leaving.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
