<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Story-Time! The hidden Scrum meeting</title>
	<atom:link href="http://kanemar.com/2008/02/14/story-time-the-hidden-scrum-meeting/feed/" rel="self" type="application/rss+xml" />
	<link>http://kanemar.com/2008/02/14/story-time-the-hidden-scrum-meeting/</link>
	<description>Adventures in Agile Software Development and Scrum</description>
	<lastBuildDate>Thu, 19 Apr 2012 09:24:37 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Zombie User Stories &#8230; User Stories that return from the dead! - Scrumology</title>
		<link>http://kanemar.com/2008/02/14/story-time-the-hidden-scrum-meeting/#comment-15044</link>
		<dc:creator><![CDATA[Zombie User Stories &#8230; User Stories that return from the dead! - Scrumology]]></dc:creator>
		<pubDate>Thu, 12 Apr 2012 06:39:56 +0000</pubDate>
		<guid isPermaLink="false">http://kanemar.wordpress.com/?p=245#comment-15044</guid>
		<description><![CDATA[[...] Write Acceptance Test for all User Stories. Without Acceptance Tests, how does a team know how much work to do? Quite simply, it&#8217;s impossible to know. And if you don&#8217;t know how large (or small) a Story is, then how would a team know if they can finish it within a Sprint? I&#8217;d recommend all Stories for the next two or three Sprints have Acceptance Tests defined before the Planning Meeting (here&#8217;s one way of achieving this). [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Write Acceptance Test for all User Stories. Without Acceptance Tests, how does a team know how much work to do? Quite simply, it&#8217;s impossible to know. And if you don&#8217;t know how large (or small) a Story is, then how would a team know if they can finish it within a Sprint? I&#8217;d recommend all Stories for the next two or three Sprints have Acceptance Tests defined before the Planning Meeting (here&#8217;s one way of achieving this). [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: &#187; Zombie User Stories &#8230; User Stories that return from the dead! &#187; Scrumology</title>
		<link>http://kanemar.com/2008/02/14/story-time-the-hidden-scrum-meeting/#comment-14625</link>
		<dc:creator><![CDATA[&#187; Zombie User Stories &#8230; User Stories that return from the dead! &#187; Scrumology]]></dc:creator>
		<pubDate>Fri, 25 Nov 2011 06:31:21 +0000</pubDate>
		<guid isPermaLink="false">http://kanemar.wordpress.com/?p=245#comment-14625</guid>
		<description><![CDATA[[...] Write Acceptance Test for all User Stories. Without Acceptance Tests, how does a team know how much work to do? Quite simply, it&#8217;s impossible to know. And if you don&#8217;t know how large (or small) a Story is, then how would a team know if they can finish it within a Sprint? I&#8217;d recommend all Stories for the next two or three Sprints have Acceptance Tests defined before the Planning Meeting (here&#8217;s one way of achieving this). [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Write Acceptance Test for all User Stories. Without Acceptance Tests, how does a team know how much work to do? Quite simply, it&#8217;s impossible to know. And if you don&#8217;t know how large (or small) a Story is, then how would a team know if they can finish it within a Sprint? I&#8217;d recommend all Stories for the next two or three Sprints have Acceptance Tests defined before the Planning Meeting (here&#8217;s one way of achieving this). [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Backlog Grooming &#171; Inevitably Agile</title>
		<link>http://kanemar.com/2008/02/14/story-time-the-hidden-scrum-meeting/#comment-14523</link>
		<dc:creator><![CDATA[Backlog Grooming &#171; Inevitably Agile]]></dc:creator>
		<pubDate>Wed, 20 Jul 2011 06:35:23 +0000</pubDate>
		<guid isPermaLink="false">http://kanemar.wordpress.com/?p=245#comment-14523</guid>
		<description><![CDATA[[...] http://kanemar.com/2008/02/14/story-time-the-hidden-scrum-meeting/ [...]]]></description>
		<content:encoded><![CDATA[<p>[...] <a href="http://kanemar.com/2008/02/14/story-time-the-hidden-scrum-meeting/" rel="nofollow">http://kanemar.com/2008/02/14/story-time-the-hidden-scrum-meeting/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zombie User Stories &#8230; User Stories that return from the dead! — Scrumology Pty Ltd</title>
		<link>http://kanemar.com/2008/02/14/story-time-the-hidden-scrum-meeting/#comment-14445</link>
		<dc:creator><![CDATA[Zombie User Stories &#8230; User Stories that return from the dead! — Scrumology Pty Ltd]]></dc:creator>
		<pubDate>Wed, 11 May 2011 20:08:21 +0000</pubDate>
		<guid isPermaLink="false">http://kanemar.wordpress.com/?p=245#comment-14445</guid>
		<description><![CDATA[[...] Write Acceptance Test for all User Stories. Without Acceptance Tests, how does a team know how much work to do? Quite simply, it&#8217;s impossible to know. And if you don&#8217;t know how large (or small) a Story is, then how would a team know if they can finish it within a Sprint? I&#8217;d recommend all Stories for the next two or three Sprints have Acceptance Tests defined before the Planning Meeting (here&#8217;s one way of achieving this). [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Write Acceptance Test for all User Stories. Without Acceptance Tests, how does a team know how much work to do? Quite simply, it&#8217;s impossible to know. And if you don&#8217;t know how large (or small) a Story is, then how would a team know if they can finish it within a Sprint? I&#8217;d recommend all Stories for the next two or three Sprints have Acceptance Tests defined before the Planning Meeting (here&#8217;s one way of achieving this). [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fabrice Aimetti</title>
		<link>http://kanemar.com/2008/02/14/story-time-the-hidden-scrum-meeting/#comment-14307</link>
		<dc:creator><![CDATA[Fabrice Aimetti]]></dc:creator>
		<pubDate>Tue, 01 Feb 2011 17:12:02 +0000</pubDate>
		<guid isPermaLink="false">http://kanemar.wordpress.com/?p=245#comment-14307</guid>
		<description><![CDATA[Hello Kane,

Your post is very interesting. I&#039;ve translated it into french :
&lt;a href=&quot;http://www.fabrice-aimetti.fr/dotclear/index.php?post/2011/02/01/Story-Time-la-reunion-Scrum-cachee&quot; rel=&quot;nofollow&quot;&gt;Story Time, la réunion Scrum cachée&lt;/a&gt;

Regards, Fabrice]]></description>
		<content:encoded><![CDATA[<p>Hello Kane,</p>
<p>Your post is very interesting. I&#8217;ve translated it into french :<br />
<a href="http://www.fabrice-aimetti.fr/dotclear/index.php?post/2011/02/01/Story-Time-la-reunion-Scrum-cachee" rel="nofollow">Story Time, la réunion Scrum cachée</a></p>
<p>Regards, Fabrice</p>
]]></content:encoded>
	</item>
</channel>
</rss>

