<?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: Getting attached to stories</title>
	<atom:link href="http://www.dancingmango.com/blog/2006/10/16/getting-attached-to-stories/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.dancingmango.com/blog/2006/10/16/getting-attached-to-stories/</link>
	<description>For more than a decade Marc has been a passionate advocate of placing the customer at the heart of business, working with clients in finance, retail, government and entertainment sectors, helping them craft compelling cross channel customer experiences.  Marc champions lean and agile approaches for making customer driven innovation happen.  He brings design thinking and creativity to clients, engaging across the organisation with a focus on delivery as well as ideas.  He is currently writing a book on Agile Experience Design to be published this Autumn.</description>
	<lastBuildDate>Sun, 25 Sep 2011 23:33:07 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Kerry Buckley</title>
		<link>http://www.dancingmango.com/blog/2006/10/16/getting-attached-to-stories/comment-page-1/#comment-3674</link>
		<dc:creator>Kerry Buckley</dc:creator>
		<pubDate>Mon, 16 Oct 2006 18:25:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.dancingmango.com/blog/2006/10/16/getting-attached-to-stories/#comment-3674</guid>
		<description>One advantage of copying the cards to a wiki if you need to access them remotely, rather than using a spreadsheet is that you can delete and rewrite them to your heart&#039;s content, and the page&#039;s history is your audit trail. We all know that no-one will ever look, but at least you can reassure people that the history isn&#039;t lost, and because it happens automatically there&#039;s no overhead.

We tend to keep the bare minimum (title, estimate and a few notes) on the index cards, and put the expanded information, including acceptance criteria, on the release plan wiki page. Apart from anything else, the less you write on the cards, the less reluctant you are to tear them up if they need changing.</description>
		<content:encoded><![CDATA[<p>One advantage of copying the cards to a wiki if you need to access them remotely, rather than using a spreadsheet is that you can delete and rewrite them to your heart&#8217;s content, and the page&#8217;s history is your audit trail. We all know that no-one will ever look, but at least you can reassure people that the history isn&#8217;t lost, and because it happens automatically there&#8217;s no overhead.</p>
<p>We tend to keep the bare minimum (title, estimate and a few notes) on the index cards, and put the expanded information, including acceptance criteria, on the release plan wiki page. Apart from anything else, the less you write on the cards, the less reluctant you are to tear them up if they need changing.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

