<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: What&#8217;s in a name?</title>
	<atom:link href="http://danrough.net/2007/03/03/whats-in-a-name/feed/" rel="self" type="application/rss+xml" />
	<link>http://danrough.net/2007/03/03/whats-in-a-name/</link>
	<description></description>
	<lastBuildDate>Sun, 11 Sep 2011 08:36:11 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: danrough</title>
		<link>http://danrough.net/2007/03/03/whats-in-a-name/#comment-83</link>
		<dc:creator><![CDATA[danrough]]></dc:creator>
		<pubDate>Wed, 21 Mar 2007 01:23:46 +0000</pubDate>
		<guid isPermaLink="false">http://danrough.wordpress.com/2007/03/03/whats-in-a-name/#comment-83</guid>
		<description><![CDATA[I&#039;m not sure that it is just a matter of getting the client involved from the beginning, more that they should be involved throughout, after all, it is their product / project, they&#039;re the ones who understand what they want best.

I think one of the main benefits of an Agile approach is that it promotes a lot more communication, which in my mind, is the main reason that a lot of projects fail. Similarly, perhaps the client wouldn&#039;t be screaming as much if they had been involved up front, at least they would have known that the team weren&#039;t meeting the scope that had been committed too for any given Iteration / Sprint.]]></description>
		<content:encoded><![CDATA[<p>I&#8217;m not sure that it is just a matter of getting the client involved from the beginning, more that they should be involved throughout, after all, it is their product / project, they&#8217;re the ones who understand what they want best.</p>
<p>I think one of the main benefits of an Agile approach is that it promotes a lot more communication, which in my mind, is the main reason that a lot of projects fail. Similarly, perhaps the client wouldn&#8217;t be screaming as much if they had been involved up front, at least they would have known that the team weren&#8217;t meeting the scope that had been committed too for any given Iteration / Sprint.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben H</title>
		<link>http://danrough.net/2007/03/03/whats-in-a-name/#comment-81</link>
		<dc:creator><![CDATA[Ben H]]></dc:creator>
		<pubDate>Mon, 19 Mar 2007 16:01:06 +0000</pubDate>
		<guid isPermaLink="false">http://danrough.wordpress.com/2007/03/03/whats-in-a-name/#comment-81</guid>
		<description><![CDATA[Srum is a nice idea and i use it to a certain degree. 

However, it doesn&#039;t really matter when the client is screaming at you and you have 4 days left to finish the project youve still got to stay all night and finish it off.

..and i know the response &quot;the client wouldn&#039;t be like that if they are truly involved from the beginning blah blah&quot;

This is not my experience of the real world.]]></description>
		<content:encoded><![CDATA[<p>Srum is a nice idea and i use it to a certain degree. </p>
<p>However, it doesn&#8217;t really matter when the client is screaming at you and you have 4 days left to finish the project youve still got to stay all night and finish it off.</p>
<p>..and i know the response &#8220;the client wouldn&#8217;t be like that if they are truly involved from the beginning blah blah&#8221;</p>
<p>This is not my experience of the real world.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: danrough</title>
		<link>http://danrough.net/2007/03/03/whats-in-a-name/#comment-69</link>
		<dc:creator><![CDATA[danrough]]></dc:creator>
		<pubDate>Sun, 04 Mar 2007 08:37:00 +0000</pubDate>
		<guid isPermaLink="false">http://danrough.wordpress.com/2007/03/03/whats-in-a-name/#comment-69</guid>
		<description><![CDATA[Thanks Wan. I&#039;ve had quite a bit of time to consider this recently and I must confess that now, I would rather we didn&#039;t refer to it as Agile or Scrum but perhaps as some of my colleagues do, that we are just taking a pragmatic approach. In some respects I think that some people might be a little less intimidated by some of the suggestions.

As I say, it&#039;s whatever works for you.]]></description>
		<content:encoded><![CDATA[<p>Thanks Wan. I&#8217;ve had quite a bit of time to consider this recently and I must confess that now, I would rather we didn&#8217;t refer to it as Agile or Scrum but perhaps as some of my colleagues do, that we are just taking a pragmatic approach. In some respects I think that some people might be a little less intimidated by some of the suggestions.</p>
<p>As I say, it&#8217;s whatever works for you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wan</title>
		<link>http://danrough.net/2007/03/03/whats-in-a-name/#comment-68</link>
		<dc:creator><![CDATA[Wan]]></dc:creator>
		<pubDate>Sat, 03 Mar 2007 23:11:36 +0000</pubDate>
		<guid isPermaLink="false">http://danrough.wordpress.com/2007/03/03/whats-in-a-name/#comment-68</guid>
		<description><![CDATA[Agreed. This has been sometimes been referred to as agile &quot;with a small a&quot;, as opposed to the strict by the book following of the &quot;Church of Agile&quot;]]></description>
		<content:encoded><![CDATA[<p>Agreed. This has been sometimes been referred to as agile &#8220;with a small a&#8221;, as opposed to the strict by the book following of the &#8220;Church of Agile&#8221;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

