<?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>scruminfo.com &#187; Scrum Articles</title>
	<atom:link href="http://scruminfo.com/wp/category/scrum-articles/feed/" rel="self" type="application/rss+xml" />
	<link>http://scruminfo.com/wp</link>
	<description>a personal expression of scrum...</description>
	<lastBuildDate>Sun, 21 Feb 2010 02:07:51 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>SEPARATE USER STORY ESTIMATES &#8211; A SIGN THAT SOMETHING IS WRONG</title>
		<link>http://scruminfo.com/wp/2009/10/23/split-user-story-estimates-a-sign-that-there-is-something-wrong/</link>
		<comments>http://scruminfo.com/wp/2009/10/23/split-user-story-estimates-a-sign-that-there-is-something-wrong/#comments</comments>
		<pubDate>Fri, 23 Oct 2009 01:50:43 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Scrum Articles]]></category>
		<category><![CDATA[Techniques]]></category>

		<guid isPermaLink="false">http://scruminfo.com/wp/?p=45</guid>
		<description><![CDATA[I once observed a practice where story cards were only estimated based on the development effort. This is problematic as it has one specific focus and not looking at the total work that needs to be completed for a story to be moved into done. Product development is not just about writing code.]]></description>
		<wfw:commentRss>http://scruminfo.com/wp/2009/10/23/split-user-story-estimates-a-sign-that-there-is-something-wrong/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A SHORT GUIDE TO AGILE USER STORIES &#8230;</title>
		<link>http://scruminfo.com/wp/2009/10/22/a-short-guide-to-agile-user-stories/</link>
		<comments>http://scruminfo.com/wp/2009/10/22/a-short-guide-to-agile-user-stories/#comments</comments>
		<pubDate>Thu, 22 Oct 2009 23:50:13 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Scrum Articles]]></category>
		<category><![CDATA[Techniques]]></category>

		<guid isPermaLink="false">http://scruminfo.com/wp/?p=43</guid>
		<description><![CDATA[I have written this article in the hope that it will remove a lot of confusion in our industry on what  a user story is. If you are transitioning from heavyweight to agile methods you may find this useful. I have not included estimation and how we manage stories on the backlog etc and [...]]]></description>
		<wfw:commentRss>http://scruminfo.com/wp/2009/10/22/a-short-guide-to-agile-user-stories/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>SCRUM POEM</title>
		<link>http://scruminfo.com/wp/2008/07/24/scrum-poem/</link>
		<comments>http://scruminfo.com/wp/2008/07/24/scrum-poem/#comments</comments>
		<pubDate>Thu, 24 Jul 2008 12:34:23 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Scrum Articles]]></category>

		<guid isPermaLink="false">http://scruminfo.com/wp/2008/07/24/scrum-poem/</guid>
		<description><![CDATA[Not sure if anyone has ever written a scrum poem so gave it a crack &#8230;..
It is a thing called scrum and
this is how it is done.
We talk and discuss
Then we create a product backlog without fuss
A backlog has many items , they call each one a story
and its not a document thats gives the [...]]]></description>
		<wfw:commentRss>http://scruminfo.com/wp/2008/07/24/scrum-poem/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>USING T-SHIRT SIZES FOR USER STORY ESTIMATION</title>
		<link>http://scruminfo.com/wp/2008/03/14/using-t-shirt-sizes-for-user-story-estimation/</link>
		<comments>http://scruminfo.com/wp/2008/03/14/using-t-shirt-sizes-for-user-story-estimation/#comments</comments>
		<pubDate>Fri, 14 Mar 2008 02:58:32 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Scrum Articles]]></category>

		<guid isPermaLink="false">http://scruminfo.com/wp/2008/03/14/using-t-shirt-sizes-for-user-story-estimation/</guid>
		<description><![CDATA[There are a number of story point scales used for estimating user stories on the product backlog.
An effective scale to use for your estimation is T-Shirt sizes.
T-SHIRT SIZES
Size                                    Points to Allocate
XS (Extra Small)                   1
S  (small)                                2
M  (medium)                         4
L  (Large)                               8
XL (extra large)                   16
XXL(extra extra large)       32
T-Shirt sizes are nonlinear so the bigger the &#8220;shirt&#8221; [...]]]></description>
		<wfw:commentRss>http://scruminfo.com/wp/2008/03/14/using-t-shirt-sizes-for-user-story-estimation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>SCRUM KANBAN EXAMPLE &#8211; TASKBOARD</title>
		<link>http://scruminfo.com/wp/2008/03/13/scrum-kanban-example-taskboard/</link>
		<comments>http://scruminfo.com/wp/2008/03/13/scrum-kanban-example-taskboard/#comments</comments>
		<pubDate>Thu, 13 Mar 2008 09:09:35 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Scrum Articles]]></category>

		<guid isPermaLink="false">http://scruminfo.com/wp/2008/03/13/scrum-kanban-example-taskboard/</guid>
		<description><![CDATA[
]]></description>
		<wfw:commentRss>http://scruminfo.com/wp/2008/03/13/scrum-kanban-example-taskboard/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
