<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Joseph Wilk &#187; Stories</title>
	<atom:link href="http://blog.josephwilk.net/tag/stories/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.josephwilk.net</link>
	<description>on AI, The Web, Usability, Testing &#38; Software process</description>
	<lastBuildDate>Tue, 26 Jul 2011 17:14:14 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.2</generator>
		<item>
		<title>Story Smells: The Valueless Story</title>
		<link>http://blog.josephwilk.net/agile/story-smells-the-valueless-story.html</link>
		<comments>http://blog.josephwilk.net/agile/story-smells-the-valueless-story.html#comments</comments>
		<pubDate>Thu, 10 Mar 2011 15:00:17 +0000</pubDate>
		<dc:creator>Joseph Wilk</dc:creator>
				<category><![CDATA[Agile]]></category>
		<category><![CDATA[Stories]]></category>

		<guid isPermaLink="false">http://blog.josephwilk.net/?p=2018</guid>
		<description><![CDATA[&#8220;Why bother discussing the value or writing it down for the stories, everybody already knows what it is&#8221; Problem The value of a story to a stakeholder is not discussed or written on a card. The group participating in story writing workshop feel there is no point in dealing with the value since it seems [...]]]></description>
		<wfw:commentRss>http://blog.josephwilk.net/agile/story-smells-the-valueless-story.html/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Story smells: In order to do X I want X</title>
		<link>http://blog.josephwilk.net/agile/story-smells-in-order-to-do-x-i-want-x.html</link>
		<comments>http://blog.josephwilk.net/agile/story-smells-in-order-to-do-x-i-want-x.html#comments</comments>
		<pubDate>Tue, 23 Nov 2010 18:40:48 +0000</pubDate>
		<dc:creator>Joseph Wilk</dc:creator>
				<category><![CDATA[Agile]]></category>
		<category><![CDATA[Stories]]></category>

		<guid isPermaLink="false">http://blog.josephwilk.net/?p=1944</guid>
		<description><![CDATA[I keep coming across story cards written like this: This is usually a tell tale sign that the why stack was not popped. The value (In order to &#60;value&#62;) has been written at the lowest possible level of abstraction, the same as the feature (I want &#60;feature&#62;). The card does not tell us why this feature [...]]]></description>
		<wfw:commentRss>http://blog.josephwilk.net/agile/story-smells-in-order-to-do-x-i-want-x.html/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Telling a good story &#8211; Rspec stories from the trenches</title>
		<link>http://blog.josephwilk.net/ruby/telling-a-good-story-rspec-stories-from-the-trenches.html</link>
		<comments>http://blog.josephwilk.net/ruby/telling-a-good-story-rspec-stories-from-the-trenches.html#comments</comments>
		<pubDate>Fri, 15 Aug 2008 16:19:55 +0000</pubDate>
		<dc:creator>Joseph Wilk</dc:creator>
				<category><![CDATA[Ruby]]></category>
		<category><![CDATA[Rspec]]></category>
		<category><![CDATA[Stories]]></category>
		<category><![CDATA[Testing]]></category>

		<guid isPermaLink="false">http://www.joesniff.co.uk/?p=125</guid>
		<description><![CDATA[I&#8217;ve been developing multiple systems using Rspec stories for a little while now. There are a lot of great resources to get you started with a taste of what you can do with stories. Some of the resources I found useful where: http://peepcode.com/products/rspec-user-stories http://blog.davidchelimsky.net/2008/6/16/slides-from-railsconf http://www.benmabey.com/2008/02/04/rspec-plain-text-stories-webrat-chunky-bacon/ http://dannorth.net/whats-in-a-story http://evang.eli.st/blog/2007/10/8/story-runner-top-to-bottom-screencast However once I had understood the basic idea [...]]]></description>
		<wfw:commentRss>http://blog.josephwilk.net/ruby/telling-a-good-story-rspec-stories-from-the-trenches.html/feed</wfw:commentRss>
		<slash:comments>12</slash:comments>
		</item>
		<item>
		<title>Rspec Stories &#8211; Keeping Steps Dry</title>
		<link>http://blog.josephwilk.net/snippets/rspec-stories-keeping-steps-dry.html</link>
		<comments>http://blog.josephwilk.net/snippets/rspec-stories-keeping-steps-dry.html#comments</comments>
		<pubDate>Wed, 30 Apr 2008 18:00:36 +0000</pubDate>
		<dc:creator>Joseph Wilk</dc:creator>
				<category><![CDATA[Snippets]]></category>
		<category><![CDATA[Rspec]]></category>
		<category><![CDATA[Ruby]]></category>
		<category><![CDATA[Stories]]></category>
		<category><![CDATA[Testing]]></category>

		<guid isPermaLink="false">http://www.joesniff.co.uk/?p=72</guid>
		<description><![CDATA[When using Rspec stories you have plain text stories which we call the &#8216;story&#8217; file and the &#8216;story steps&#8217; file that maps the plain text story to programmatic code. Generally you end up with your story files not being DRY. This is not a worry, your stories are the domain specific languages detailing your acceptance/integration [...]]]></description>
		<wfw:commentRss>http://blog.josephwilk.net/snippets/rspec-stories-keeping-steps-dry.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

