<?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 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>Agile Business Analysis &#8211; We really dont need it !</title>
		<link>http://scruminfo.com/wp/2012/05/03/agile-business-analysis-we-really-dont-need-it/</link>
		<comments>http://scruminfo.com/wp/2012/05/03/agile-business-analysis-we-really-dont-need-it/#comments</comments>
		<pubDate>Thu, 03 May 2012 05:08:59 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Acceptance Criteria]]></category>
		<category><![CDATA[Agile In General]]></category>
		<category><![CDATA[Given-When-Then]]></category>
		<category><![CDATA[Scrum Articles]]></category>

		<guid isPermaLink="false">http://scruminfo.com/wp/?p=169</guid>
		<description><![CDATA[I have seen many questions, debates and statements made about the &#8216;Business Analyst Role&#8217; in an agile environment. I am hoping that this post will help answer, clarify or stimulate your own alternative thoughts and views. I have just dumped my thoughts so excuse the format and lack of structure. Over the years I feel]]></description>
		<wfw:commentRss>http://scruminfo.com/wp/2012/05/03/agile-business-analysis-we-really-dont-need-it/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Most agile implementations revert to old ways, perhaps its the traffic light</title>
		<link>http://scruminfo.com/wp/2012/02/13/most-agile-implementations-revert-to-old-ways-perhaps-its-the-traffic-light/</link>
		<comments>http://scruminfo.com/wp/2012/02/13/most-agile-implementations-revert-to-old-ways-perhaps-its-the-traffic-light/#comments</comments>
		<pubDate>Mon, 13 Feb 2012 08:21:50 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Scrum Articles]]></category>

		<guid isPermaLink="false">http://scruminfo.com/wp/?p=148</guid>
		<description><![CDATA[I had a thought today and I looked back long ago to when I was not using agile and how my project managers reported. In most organisations we have the so called &#8216;traffic light&#8217; status report. I spent some time reflecting on experiences and it is very easy to see how agile really does take]]></description>
		<wfw:commentRss>http://scruminfo.com/wp/2012/02/13/most-agile-implementations-revert-to-old-ways-perhaps-its-the-traffic-light/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 Resistance</title>
		<link>http://scruminfo.com/wp/2012/02/02/agile-resistance/</link>
		<comments>http://scruminfo.com/wp/2012/02/02/agile-resistance/#comments</comments>
		<pubDate>Thu, 02 Feb 2012 04:42:39 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Agile In General]]></category>
		<category><![CDATA[Scrum Articles]]></category>

		<guid isPermaLink="false">http://scruminfo.com/wp/?p=99</guid>
		<description><![CDATA[I feel that as agilists we forget how agile can impact people. Agile is trying to undo decades of behaviour and practices, it is a massive change for some. Agile does not fail it is people who fail. Every failure I have been in has resulted in failure only because of non acceptance or where]]></description>
		<wfw:commentRss>http://scruminfo.com/wp/2012/02/02/agile-resistance/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>
	</channel>
</rss>

