<?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>Advanced Topics In Scrum &#187; slack</title>
	<atom:link href="http://advancedtopicsinscrum.com/tag/slack/feed/" rel="self" type="application/rss+xml" />
	<link>http://advancedtopicsinscrum.com</link>
	<description>Techniques for Applied Scrum</description>
	<lastBuildDate>Mon, 12 Apr 2010 13:36:59 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.1</generator>
		<item>
		<title>Is it ok to have Placeholder Stories?</title>
		<link>http://advancedtopicsinscrum.com/faq/is-it-ok-to-have-placeholder-stories/</link>
		<comments>http://advancedtopicsinscrum.com/faq/is-it-ok-to-have-placeholder-stories/#comments</comments>
		<pubDate>Fri, 16 Oct 2009 03:30:07 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[FAQ]]></category>
		<category><![CDATA[known unknowns]]></category>
		<category><![CDATA[placeholder story]]></category>
		<category><![CDATA[planning]]></category>
		<category><![CDATA[slack]]></category>
		<category><![CDATA[sprint planning]]></category>
		<category><![CDATA[story]]></category>

		<guid isPermaLink="false">http://advancedtopicsinscrum.com/?p=338</guid>
		<description><![CDATA[Using Place holder stories is a a method to manage these “known unknowns”.]]></description>
			<content:encoded><![CDATA[<h3>Choose:</h3>
<ol>
<li><img class="alignleft size-medium wp-image-341" style="margin: 5px; border: 1px solid black;" title="place-holder-story-scrum-agile-slack" src="http://advancedtopicsinscrum.com/wp-content/uploads/2009/10/place-holder-story-scrum-agile-slack-225x300.jpg" alt="place-holder-story-scrum-agile-slack" width="225" height="300" />A placeholder story is a sign of sloppy planning</li>
<li>All work should be known ahead of time and planned during sprint planning</li>
<li>Yes, this allows the Product Owner to dump things into the sprint as needed.</li>
<li>Sometimes we have a history of unexpected bugs/issues of handle it now. This allows us to track how much of that is showing up and leave some slack for when it does.</li>
<li>We often have work we know we will have to do but, don&#8217;t know what it is yet.</li>
</ol>
<p><strong>Comment</strong>: This is a way to track how much unknown work is showing up and manage the amount by triggering a conversation when needed. One of the most common issues for scrum teams is what to do about work that we expect to have to do during a Sprint, but don’t actually know the details about yet, such as bugs we have to fix in existing systems, or expected sales support efforts. Using Place holder stories is a a method to manage these “known unknowns”.</p>
]]></content:encoded>
			<wfw:commentRss>http://advancedtopicsinscrum.com/faq/is-it-ok-to-have-placeholder-stories/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

