<?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/"
		>
<channel>
	<title>Comments on: Importance Of Attitude in Agile Projects</title>
	<atom:link href="http://blog.xebia.com/2008/03/11/importance-of-attitude-in-agile-projects/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.xebia.com/2008/03/11/importance-of-attitude-in-agile-projects/</link>
	<description>Software development done right!</description>
	<lastBuildDate>Wed, 08 Feb 2012 14:41:38 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: AVH</title>
		<link>http://blog.xebia.com/2008/03/11/importance-of-attitude-in-agile-projects/#comment-37916</link>
		<dc:creator>AVH</dc:creator>
		<pubDate>Fri, 14 Mar 2008 11:06:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.xebia.com/2008/03/11/importance-of-attitude-in-agile-projects/#comment-37916</guid>
		<description>May be you should read this

http://www.infoq.com/news/2008/03/should-customer-embrace-agile</description>
		<content:encoded><![CDATA[<p>May be you should read this</p>
<p><a href="http://www.infoq.com/news/2008/03/should-customer-embrace-agile" rel="nofollow">http://www.infoq.com/news/2008/03/should-customer-embrace-agile</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Serge Beaumont</title>
		<link>http://blog.xebia.com/2008/03/11/importance-of-attitude-in-agile-projects/#comment-37664</link>
		<dc:creator>Serge Beaumont</dc:creator>
		<pubDate>Wed, 12 Mar 2008 10:47:41 +0000</pubDate>
		<guid isPermaLink="false">http://blog.xebia.com/2008/03/11/importance-of-attitude-in-agile-projects/#comment-37664</guid>
		<description>&quot;A good attitude&quot; is not an absolute term. What is a good attitude depends on the situation. A good attitude for working in an Agile team is different from the attitude needed for a successful waterfall team. Much is the same, but much is also different.

Having said that, attitude has more impact in an agile team. Instead of being a tool of the process, team members are expected to show more responsibility. Like I&#039;ve said many times, agile is not a place for cowboys. Without a responsible attitude agile will certainly break down.

So attitude is a coin with two sides: it can be a major successfactor, but it can be a risk as well...</description>
		<content:encoded><![CDATA[<p>&#8220;A good attitude&#8221; is not an absolute term. What is a good attitude depends on the situation. A good attitude for working in an Agile team is different from the attitude needed for a successful waterfall team. Much is the same, but much is also different.</p>
<p>Having said that, attitude has more impact in an agile team. Instead of being a tool of the process, team members are expected to show more responsibility. Like I&#8217;ve said many times, agile is not a place for cowboys. Without a responsible attitude agile will certainly break down.</p>
<p>So attitude is a coin with two sides: it can be a major successfactor, but it can be a risk as well&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Raghu</title>
		<link>http://blog.xebia.com/2008/03/11/importance-of-attitude-in-agile-projects/#comment-37610</link>
		<dc:creator>Raghu</dc:creator>
		<pubDate>Wed, 12 Mar 2008 03:56:38 +0000</pubDate>
		<guid isPermaLink="false">http://blog.xebia.com/2008/03/11/importance-of-attitude-in-agile-projects/#comment-37610</guid>
		<description>When i was attending &lt;a href=\&quot;http://agileindia.org/agilencr08/index\&quot; rel=&quot;nofollow&quot;&gt; Agile NCR conference&lt;/a&gt;, I liked this point from &lt;a href=\&quot;http://www.scrumalliance.org/profiles/49-pete-deemer\&quot; rel=&quot;nofollow&quot;&gt;Pete Deemer&lt;/a&gt;
\&quot;What do you do when the deadline is over and the boss says do whatever it takes\&quot;. 

At that point getting rid of testing, code-quality, necessary documentation would be a bad idea. If deadline is over so be it. 

At least you have delivered a partially complete good quality product because it was developed in slices. At least agile should let you raise the issue well in advance. I will be possible to continue if the deadline is made available. Yes no one needs incomplete products. So whats the solution? There may be no solution. 

The problem lies in how you compute deadlines. You might like to compute deadlines based on velocity and revise it accordingly. But this may not always be possible. Deadlines may still be forced on a project based on financial and time constraints. And because velocity wont be known in advance the victim will always be scope. Unless there is a deadline that was luckily (experience?) appropriate.

I also liked &lt;a href=\&quot;http://www.jroller.com/njain/\&quot; rel=&quot;nofollow&quot;&gt;Naresh’s&lt;/a&gt; conclusion that one needs courage and discipline to do agile. This is probably very important so that the team does not misuse the freedom.

Also wanted to add that velocity will be higher in agile due to the leanness so agile is more likely to deliver earlier. 

However deadline convergence is all about proabblity.
The accuracy of a computed real deadline is higher only in later stages. And its possible the deadline will need to shift and its possible the deadline can\&#039;t be moved.

That said the limitation of deadline being wrong is a problem for both waterfall and agile. In waterfall its much more a problem. In agile at least the client will not discover during UAT that he wanted something else.

Coming back to deadline everyone including the client is aware of the risk in imposing a deadline. Sometimes they are willing to change the deadline if they feel satisfied about the efforts that were put in. Its important to keep lax time without being unproductive. Otherwise the client would feel he is being taken for a ride. Hence the need for a mature, responsible, disciplined, professional  team.</description>
		<content:encoded><![CDATA[<p>When i was attending <a href=\"http://agileindia.org/agilencr08/index\" rel="nofollow"> Agile NCR conference</a>, I liked this point from <a href=\"http://www.scrumalliance.org/profiles/49-pete-deemer\" rel="nofollow">Pete Deemer</a><br />
\&#8221;What do you do when the deadline is over and the boss says do whatever it takes\&#8221;. </p>
<p>At that point getting rid of testing, code-quality, necessary documentation would be a bad idea. If deadline is over so be it. </p>
<p>At least you have delivered a partially complete good quality product because it was developed in slices. At least agile should let you raise the issue well in advance. I will be possible to continue if the deadline is made available. Yes no one needs incomplete products. So whats the solution? There may be no solution. </p>
<p>The problem lies in how you compute deadlines. You might like to compute deadlines based on velocity and revise it accordingly. But this may not always be possible. Deadlines may still be forced on a project based on financial and time constraints. And because velocity wont be known in advance the victim will always be scope. Unless there is a deadline that was luckily (experience?) appropriate.</p>
<p>I also liked <a href=\"http://www.jroller.com/njain/\" rel="nofollow">Naresh’s</a> conclusion that one needs courage and discipline to do agile. This is probably very important so that the team does not misuse the freedom.</p>
<p>Also wanted to add that velocity will be higher in agile due to the leanness so agile is more likely to deliver earlier. </p>
<p>However deadline convergence is all about proabblity.<br />
The accuracy of a computed real deadline is higher only in later stages. And its possible the deadline will need to shift and its possible the deadline can\&#8217;t be moved.</p>
<p>That said the limitation of deadline being wrong is a problem for both waterfall and agile. In waterfall its much more a problem. In agile at least the client will not discover during UAT that he wanted something else.</p>
<p>Coming back to deadline everyone including the client is aware of the risk in imposing a deadline. Sometimes they are willing to change the deadline if they feel satisfied about the efforts that were put in. Its important to keep lax time without being unproductive. Otherwise the client would feel he is being taken for a ride. Hence the need for a mature, responsible, disciplined, professional  team.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anurag</title>
		<link>http://blog.xebia.com/2008/03/11/importance-of-attitude-in-agile-projects/#comment-37589</link>
		<dc:creator>Anurag</dc:creator>
		<pubDate>Wed, 12 Mar 2008 01:17:15 +0000</pubDate>
		<guid isPermaLink="false">http://blog.xebia.com/2008/03/11/importance-of-attitude-in-agile-projects/#comment-37589</guid>
		<description>I feel a good attitude on customer and development side can even make waterfall work.</description>
		<content:encoded><![CDATA[<p>I feel a good attitude on customer and development side can even make waterfall work.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- This Quick Cache file was built for (  blog.xebia.com/2008/03/11/importance-of-attitude-in-agile-projects/feed/ ) in 0.54478 seconds, on Feb 9th, 2012 at 8:46 pm UTC. -->
<!-- This Quick Cache file will automatically expire ( and be re-built automatically ) on Feb 9th, 2012 at 9:46 pm UTC -->
