<?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>Agile Roots Conference 2010 &#187; Manifesto</title>
	<atom:link href="http://www.agileroots.com/tag/manifesto/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.agileroots.com</link>
	<description>Building Great Software</description>
	<lastBuildDate>Fri, 22 Jul 2011 12:39:41 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>What? Why?</title>
		<link>http://www.agileroots.com/2009/what-why/</link>
		<comments>http://www.agileroots.com/2009/what-why/#comments</comments>
		<pubDate>Tue, 07 Apr 2009 16:53:07 +0000</pubDate>
		<dc:creator>Andrew Shafer</dc:creator>
				<category><![CDATA[2009 Conference]]></category>
		<category><![CDATA[Program]]></category>
		<category><![CDATA[Agile]]></category>
		<category><![CDATA[Manifesto]]></category>
		<category><![CDATA[Why]]></category>

		<guid isPermaLink="false">http://www.agileroots.com/?p=72</guid>
		<description><![CDATA[What is Agile Roots and why should you be there? What is the vision and purpose? Agile Roots was born out of conversations started at the Salt Lake City Agile Roundtable between practitioners on the Agile path. We all recognized similar struggles and anti-patterns  in Agile implementations and in many cases these problems didn&#8217;t seem [...]]]></description>
			<content:encoded><![CDATA[<p>What is Agile Roots and why should you be there?</p>
<p>What is the vision and purpose?</p>
<p>Agile Roots was born out of conversations started at the Salt Lake City Agile Roundtable between practitioners on the Agile path.</p>
<p>We all recognized similar struggles and anti-patterns  in Agile implementations and in many cases these problems didn&#8217;t seem to be improving.</p>
<p>In discussion, the root cause of the problem was almost always neglecting the <a href="http://agilemanifesto.org/" target="_blank">Agile manifesto&#8217;s balancing values</a> and <a href="http://agilemanifesto.org/principles.html" target="_blank">principles</a>, manifesting in empty &#8216;Agile&#8217; rituals.</p>
<p>Furthermore, we identified a key factor for successful Agile adoption as management level understanding and support for the Agile initiative. Executives who truly valued the ideas and principles were often the difference between a high functioning Agile team and a mandated buzzword compliant &#8216;Agile&#8217; implementation or a decimated grassroots &#8216;Agile uprising&#8217;.</p>
<p>Our vision was to bring all the different groups that represent an Agile team together, candidly reflect on the values and principles, then build on our experiences and understanding to improve the future.</p>
<p>The goals for the conference are to:</p>
<ul>
<li>revisit the Agile Manifesto&#8217;s values and principles</li>
<li>discuss the current state of Agile practice, good, bad and ugly in relation to the Agile values</li>
<li>encourage Agile practitioners to never stop uncovering better ways of developing software</li>
<li>vitalize our Agile practices (by doing &#8216;it&#8217; and helping others to do &#8216;it&#8217;.)</li>
</ul>
<p>The Agile Manifesto wasn&#8217;t the destination, it was a milestone marking a new beginning.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.agileroots.com/2009/what-why/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

