<?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: The Easy Way to Writing Good User Stories</title>
	<atom:link href="http://www.codesqueeze.com/the-easy-way-to-writing-good-user-stories/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.codesqueeze.com/the-easy-way-to-writing-good-user-stories/</link>
	<description>Ideas for building efficient developers and software</description>
	<lastBuildDate>Mon, 30 Jan 2012 11:03:44 -0500</lastBuildDate>
	
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: The Best Resources About User Stories &#171; Product Owner for web applications</title>
		<link>http://www.codesqueeze.com/the-easy-way-to-writing-good-user-stories/#comment-10156</link>
		<dc:creator>The Best Resources About User Stories &#171; Product Owner for web applications</dc:creator>
		<pubDate>Sun, 01 Jan 2012 14:44:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.codesqueeze.com/the-easy-way-to-writing-good-user-stories/#comment-10156</guid>
		<description>[...] The Easy Way to Writing Good User Stories [...]</description>
		<content:encoded><![CDATA[<p>[...] The Easy Way to Writing Good User Stories [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: susan</title>
		<link>http://www.codesqueeze.com/the-easy-way-to-writing-good-user-stories/#comment-10077</link>
		<dc:creator>susan</dc:creator>
		<pubDate>Wed, 13 Apr 2011 22:03:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.codesqueeze.com/the-easy-way-to-writing-good-user-stories/#comment-10077</guid>
		<description>I don&#039;t think stories should list &quot;features&quot;as this narrows the discussion before designers or developers can try to solve the problem. Stories should talk about capabilities or actions. 

Also, if the story is about &quot;want&quot; we don&#039;t understand that they are about user need versus preference.

As a [role], I need [action] because [reason]
As a [role], I can [action]
As a [role], I can [action] so that [reason] 

This is what has worked for my teams - my two cents!

s</description>
		<content:encoded><![CDATA[<p>I don&#8217;t think stories should list &#8220;features&#8221;as this narrows the discussion before designers or developers can try to solve the problem. Stories should talk about capabilities or actions. </p>
<p>Also, if the story is about &#8220;want&#8221; we don&#8217;t understand that they are about user need versus preference.</p>
<p>As a [role], I need [action] because [reason]<br />
As a [role], I can [action]<br />
As a [role], I can [action] so that [reason] </p>
<p>This is what has worked for my teams &#8211; my two cents!</p>
<p>s</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Die besten Ressourcen zu User Stories &#171; Produktmanagement und Vermarktung von Internet-Anwendungen</title>
		<link>http://www.codesqueeze.com/the-easy-way-to-writing-good-user-stories/#comment-10070</link>
		<dc:creator>Die besten Ressourcen zu User Stories &#171; Produktmanagement und Vermarktung von Internet-Anwendungen</dc:creator>
		<pubDate>Tue, 22 Mar 2011 09:07:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.codesqueeze.com/the-easy-way-to-writing-good-user-stories/#comment-10070</guid>
		<description>[...] The Easy Way to Writing Good User Stories [...]</description>
		<content:encoded><![CDATA[<p>[...] The Easy Way to Writing Good User Stories [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David</title>
		<link>http://www.codesqueeze.com/the-easy-way-to-writing-good-user-stories/#comment-10035</link>
		<dc:creator>David</dc:creator>
		<pubDate>Mon, 29 Nov 2010 13:14:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.codesqueeze.com/the-easy-way-to-writing-good-user-stories/#comment-10035</guid>
		<description>Traditionally, engineers are not good at writing, and software engineers can only write code (presumably). Writing about user experiences is a good approach but requirements specs are still necessary, along with design documents.</description>
		<content:encoded><![CDATA[<p>Traditionally, engineers are not good at writing, and software engineers can only write code (presumably). Writing about user experiences is a good approach but requirements specs are still necessary, along with design documents.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: User stories? &#171; The Software Configuration Revolution Blog</title>
		<link>http://www.codesqueeze.com/the-easy-way-to-writing-good-user-stories/#comment-10028</link>
		<dc:creator>User stories? &#171; The Software Configuration Revolution Blog</dc:creator>
		<pubDate>Mon, 15 Nov 2010 14:48:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.codesqueeze.com/the-easy-way-to-writing-good-user-stories/#comment-10028</guid>
		<description>[...] to happen without having to initially go into too much detail (luckily I found a great reference here. With that Steve and agreed that our first collaboration would be to successfully act out the [...]</description>
		<content:encoded><![CDATA[<p>[...] to happen without having to initially go into too much detail (luckily I found a great reference here. With that Steve and agreed that our first collaboration would be to successfully act out the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Agile disciplines in architecture: Test Driven Architecture &#171; The Agile Architect</title>
		<link>http://www.codesqueeze.com/the-easy-way-to-writing-good-user-stories/#comment-9981</link>
		<dc:creator>Agile disciplines in architecture: Test Driven Architecture &#171; The Agile Architect</dc:creator>
		<pubDate>Mon, 30 Aug 2010 02:27:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.codesqueeze.com/the-easy-way-to-writing-good-user-stories/#comment-9981</guid>
		<description>[...] key aspect of Scrum User Stories is the inclusion of Acceptance Criteria.  Acceptance Criteria serve to elaborate or further [...]</description>
		<content:encoded><![CDATA[<p>[...] key aspect of Scrum User Stories is the inclusion of Acceptance Criteria.  Acceptance Criteria serve to elaborate or further [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Confluence: Development Guidelines</title>
		<link>http://www.codesqueeze.com/the-easy-way-to-writing-good-user-stories/#comment-3499</link>
		<dc:creator>Confluence: Development Guidelines</dc:creator>
		<pubDate>Fri, 13 Feb 2009 19:20:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.codesqueeze.com/the-easy-way-to-writing-good-user-stories/#comment-3499</guid>
		<description>&lt;strong&gt;Scrum Development Process...&lt;/strong&gt;

this page contains references to the Scrum development process   About Scrum  What is Scrum?...</description>
		<content:encoded><![CDATA[<p><strong>Scrum Development Process&#8230;</strong></p>
<p>this page contains references to the Scrum development process   About Scrum  What is Scrum?&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: User Stories &#171; Peltier On Software</title>
		<link>http://www.codesqueeze.com/the-easy-way-to-writing-good-user-stories/#comment-2905</link>
		<dc:creator>User Stories &#171; Peltier On Software</dc:creator>
		<pubDate>Sat, 25 Oct 2008 15:12:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.codesqueeze.com/the-easy-way-to-writing-good-user-stories/#comment-2905</guid>
		<description>[...] are conducive to wordiness. One suggestion to mitigate this risk is to write them initially on index cards&#8211;presumably if you&#8217;ve filled up the card, you know you&#8217;ve written enough or too [...]</description>
		<content:encoded><![CDATA[<p>[...] are conducive to wordiness. One suggestion to mitigate this risk is to write them initially on index cards&#8211;presumably if you&#8217;ve filled up the card, you know you&#8217;ve written enough or too [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bookmarks about Writing</title>
		<link>http://www.codesqueeze.com/the-easy-way-to-writing-good-user-stories/#comment-2815</link>
		<dc:creator>Bookmarks about Writing</dc:creator>
		<pubDate>Sat, 20 Sep 2008 01:14:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.codesqueeze.com/the-easy-way-to-writing-good-user-stories/#comment-2815</guid>
		<description>[...] - bookmarked by 6 members originally found by zaidlearn on 2008-08-25  The Easy Way to Writing Good User Stories  http://www.codesqueeze.com/the-easy-way-to-writing-good-user-stories/ - bookmarked by 4 members [...]</description>
		<content:encoded><![CDATA[<p>[...] &#8211; bookmarked by 6 members originally found by zaidlearn on 2008-08-25  The Easy Way to Writing Good User Stories  <a href="http://www.codesqueeze.com/the-easy-way-to-writing-good-user-stories/" rel="nofollow">http://www.codesqueeze.com/the.....r-stories/</a> &#8211; bookmarked by 4 members [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Russell Ball</title>
		<link>http://www.codesqueeze.com/the-easy-way-to-writing-good-user-stories/#comment-2760</link>
		<dc:creator>Russell Ball</dc:creator>
		<pubDate>Sun, 24 Aug 2008 05:02:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.codesqueeze.com/the-easy-way-to-writing-good-user-stories/#comment-2760</guid>
		<description>Nice post max.

This would have come in handy when we first started down the agile path in my old job. After much dinking around, I think we got the story card part down right, but never figured out the formula for user acceptance testing that was as concise and effective as you just described.

Now if I can only get my current employer to get on the Agile bandwagon...sigh...</description>
		<content:encoded><![CDATA[<p>Nice post max.</p>
<p>This would have come in handy when we first started down the agile path in my old job. After much dinking around, I think we got the story card part down right, but never figured out the formula for user acceptance testing that was as concise and effective as you just described.</p>
<p>Now if I can only get my current employer to get on the Agile bandwagon&#8230;sigh&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

