<?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 agile, where I started was scrum ...</description>
	<lastBuildDate>Thu, 02 Feb 2012 04:42:39 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Agile Restrospectives</title>
		<link>http://scruminfo.com/wp/2012/02/02/agile-restrospectives/</link>
		<comments>http://scruminfo.com/wp/2012/02/02/agile-restrospectives/#comments</comments>
		<pubDate>Thu, 02 Feb 2012 03:22:56 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Agile In General]]></category>
		<category><![CDATA[Scrum Articles]]></category>
		<category><![CDATA[Techniques]]></category>

		<guid isPermaLink="false">http://scruminfo.com/wp/?p=91</guid>
		<description><![CDATA[Agile retrospectives are all about getting the team to self-reflect, provide unified feedback and from that feedback take actions to self-improve. I saw the feedback model for individuals and thought that it could easily be adapted for retrospectives and seems to offer much more than a simple what went bad what went wrong practice. Retrospective]]></description>
		<wfw:commentRss>http://scruminfo.com/wp/2012/02/02/agile-restrospectives/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Scrum Themes</title>
		<link>http://scruminfo.com/wp/2010/11/25/scrum-themes/</link>
		<comments>http://scruminfo.com/wp/2010/11/25/scrum-themes/#comments</comments>
		<pubDate>Thu, 25 Nov 2010 03:54:09 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Scrum Articles]]></category>
		<category><![CDATA[Techniques]]></category>

		<guid isPermaLink="false">http://scruminfo.com/wp/?p=69</guid>
		<description><![CDATA[SYNOPSIS There is a lot of confusion amongst scrum practitioners on what a theme is.I have seen articles that talk about the theme for a sprint (I see a sprint theme as a goal.) I cannot say that this is incorrect as it depends on the perception of the individual. This article provides you with]]></description>
		<wfw:commentRss>http://scruminfo.com/wp/2010/11/25/scrum-themes/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<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]]></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]]></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>1</slash:comments>
		</item>
	</channel>
</rss>

