<?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>Paul Moser &#187; Agile Manifesto</title>
	<atom:link href="http://blog.paulmoser.co.uk/index.php/category/software/agile/agile-manifesto/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.paulmoser.co.uk</link>
	<description>So much to learn but so little time</description>
	<lastBuildDate>Thu, 17 Sep 2009 21:28:01 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>The Agile Manifesto is often only partially quoted</title>
		<link>http://blog.paulmoser.co.uk/index.php/2007/01/25/the-agile-manifesto-is-often-only-partially-quoted/</link>
		<comments>http://blog.paulmoser.co.uk/index.php/2007/01/25/the-agile-manifesto-is-often-only-partially-quoted/#comments</comments>
		<pubDate>Thu, 25 Jan 2007 22:59:56 +0000</pubDate>
		<dc:creator>Paul</dc:creator>
				<category><![CDATA[Agile]]></category>
		<category><![CDATA[Agile Manifesto]]></category>

		<guid isPermaLink="false">http://blog.paulmoser.co.uk/index.php/2007/01/25/the-agile-manifesto-is-often-only-partially-quoted/</guid>
		<description><![CDATA[If I was to ask you to quote the Agile Manifesto what would you say?


People and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan

That is, whilst there is value in those items on the right, we value the items on the left more.&#8221;

That&#8217;s what [...]]]></description>
			<content:encoded><![CDATA[<p>If I was to ask you to quote the Agile Manifesto what would you say?</p>
<blockquote><p><center></p>
<ul>
<li><strong>People and interactions</strong> over processes and tools</li>
<li><strong>Working software</strong> over comprehensive documentation</li>
<li><strong>Customer collaboration</strong> over contract negotiation</li>
<li><strong>Responding to change</strong> over following a plan</li>
</ul>
<p>That is, whilst there is value in those items on the right, we value the items on the left more.&#8221;</p>
<p></center></p></blockquote>
<p>That&#8217;s what I&#8217;d say and what I&#8217;ve heard others say, however it isn&#8217;t actually all of the Agile Manifesto, there are a couple more lines at the start.</p>
<blockquote><p><center>We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:</p>
<p></center></p></blockquote>
<p>It&#8217;s a shame these get missed because there is a lot in them. &#8220;We are uncovering&#8221;, note the tense here, it is present not past, it is still ongoing, we are still learning. &#8220;Better ways&#8221; &#8211; by saying better rather than best it&#8217;s acknowledged that this isn&#8217;t the definitive answer or that any previous methods didn&#8217;t work at all. &#8220;By doing it and helping other do it&#8221; &#8211; this is not some untested theory, this has been reached through real world experience.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.paulmoser.co.uk/index.php/2007/01/25/the-agile-manifesto-is-often-only-partially-quoted/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
