<?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 ...</description>
	<lastBuildDate>Fri, 18 May 2012 03:33:22 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Quick Overview of Acceptance Criteria</title>
		<link>http://scruminfo.com/wp/2012/02/14/quick-overview-of-acceptance-criteria/</link>
		<comments>http://scruminfo.com/wp/2012/02/14/quick-overview-of-acceptance-criteria/#comments</comments>
		<pubDate>Tue, 14 Feb 2012 00:29:35 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Acceptance Criteria]]></category>
		<category><![CDATA[Given-When-Then]]></category>
		<category><![CDATA[Techniques]]></category>

		<guid isPermaLink="false">http://scruminfo.com/wp/?p=155</guid>
		<description><![CDATA[I think the terms acceptance criteria, acceptance tests etc have caused a lot of confusion, in some environments they are separate, in others they are blurred. I always strive to ensure that the acceptance criteria for a theme, epic or story is defined. This acceptance criteria is the outcome and agreement with stakeholders, customers and]]></description>
		<wfw:commentRss>http://scruminfo.com/wp/2012/02/14/quick-overview-of-acceptance-criteria/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>User stories as requirements is a dangerous thing on enterprise projects</title>
		<link>http://scruminfo.com/wp/2012/02/12/user-stories-as-requirements-is-a-dangerous-thing-on-enterprise-projects/</link>
		<comments>http://scruminfo.com/wp/2012/02/12/user-stories-as-requirements-is-a-dangerous-thing-on-enterprise-projects/#comments</comments>
		<pubDate>Sun, 12 Feb 2012 23:37:44 +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=135</guid>
		<description><![CDATA[I have written this article in the hope that it will help people avoid experiencing the mess that I have seen companies get themselves into on enterprise projects. I say enterprise projects here and this refers to your large program / project corporate environment. On small projects, other environments or in a &#8216;heaven&#8217; scenario where]]></description>
		<wfw:commentRss>http://scruminfo.com/wp/2012/02/12/user-stories-as-requirements-is-a-dangerous-thing-on-enterprise-projects/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<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>
	</channel>
</rss>

