<?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; Techniques</title>
	<atom:link href="http://scruminfo.com/wp/category/techniques/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>A SMART way for setting goals&#8230;</title>
		<link>http://scruminfo.com/wp/2010/02/21/a-smart-way-for-setting-goals/</link>
		<comments>http://scruminfo.com/wp/2010/02/21/a-smart-way-for-setting-goals/#comments</comments>
		<pubDate>Sun, 21 Feb 2010 01:53:27 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Techniques]]></category>

		<guid isPermaLink="false">http://scruminfo.com/wp/?p=62</guid>
		<description><![CDATA[What is SMART? 
SMART is a simple technique that helps you set goals effectively, be it product, organisational, project or for sprints. This is an effective tool to include in your Scrum techniques.
What does SMART stand for?
Specific
Measurable
Agreed
Realistic
Timebound
SPECIFIC
When setting our goals we do not want them to be a general statement, goals must be specific so [...]]]></description>
		<wfw:commentRss>http://scruminfo.com/wp/2010/02/21/a-smart-way-for-setting-goals/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>SMALL THINGS TO MAKE THE DAY COUNT&#8230;</title>
		<link>http://scruminfo.com/wp/2009/10/23/small-things-to-to-make-the-day-more-fun/</link>
		<comments>http://scruminfo.com/wp/2009/10/23/small-things-to-to-make-the-day-more-fun/#comments</comments>
		<pubDate>Fri, 23 Oct 2009 03:36:49 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Techniques]]></category>

		<guid isPermaLink="false">http://scruminfo.com/wp/?p=49</guid>
		<description><![CDATA[Recently I was working in an agile environment where everyday one of the employees would use the local newspaper that contained a general knowledge quiz. Everyone in the group would get together for 5 minutes while he read out questions and everyone would attempt to answer.
It was such a small thing but it became a [...]]]></description>
		<wfw:commentRss>http://scruminfo.com/wp/2009/10/23/small-things-to-to-make-the-day-more-fun/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<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>THE 5 WHY&#8217;s FOR ROOT CAUSE ANALYSIS:</title>
		<link>http://scruminfo.com/wp/2008/10/24/the-5-whys-for-root-cause-analysis/</link>
		<comments>http://scruminfo.com/wp/2008/10/24/the-5-whys-for-root-cause-analysis/#comments</comments>
		<pubDate>Fri, 24 Oct 2008 03:26:02 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Techniques]]></category>

		<guid isPermaLink="false">http://scruminfo.com/wp/?p=22</guid>
		<description><![CDATA[A very simple technique to find out the root cause of a problem is to use the 5 Why&#8217;s. The number 5 is
just a general guideline and sometimes it may take a lot more or a lot less &#8220;why&#8221; questions to arrive at the root cause for a given problem.
The beauty of this technique is [...]]]></description>
		<wfw:commentRss>http://scruminfo.com/wp/2008/10/24/the-5-whys-for-root-cause-analysis/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
