<?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: Agile is an Attitude, Not a Method</title>
	<atom:link href="http://blog.sciodev.com/2008/11/20/agile-is-an-attitude-not-a-method/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.sciodev.com/2008/11/20/agile-is-an-attitude-not-a-method/</link>
	<description>Hot Thoughts about SaaS, On-Demand Business and Technology</description>
	<lastBuildDate>Tue, 01 Jun 2010 15:03:34 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: CleverWorkarounds &#187; &#8220;Governance Man&#8221; has fallen into my trap! :-)</title>
		<link>http://blog.sciodev.com/2008/11/20/agile-is-an-attitude-not-a-method/comment-page-1/#comment-105</link>
		<dc:creator>CleverWorkarounds &#187; &#8220;Governance Man&#8221; has fallen into my trap! :-)</dc:creator>
		<pubDate>Sun, 29 Mar 2009 23:47:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sciodev.com/?p=25#comment-105</guid>
		<description>[...] Woodward about the topic of rigour and attitude to make Scrum projects a success. I had read this terrific real life story on the attitude factor required in Agile and was interested in Andrew’s experience with this, specifically in the SharePoint realm. Andrew [...]</description>
		<content:encoded><![CDATA[<p>[...] Woodward about the topic of rigour and attitude to make Scrum projects a success. I had read this terrific real life story on the attitude factor required in Agile and was interested in Andrew’s experience with this, specifically in the SharePoint realm. Andrew [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Culmsee</title>
		<link>http://blog.sciodev.com/2008/11/20/agile-is-an-attitude-not-a-method/comment-page-1/#comment-77</link>
		<dc:creator>Paul Culmsee</dc:creator>
		<pubDate>Mon, 02 Mar 2009 06:38:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sciodev.com/?p=25#comment-77</guid>
		<description>This article nails it totally and goes way beyond scrum. Readers who strongly identify with this may like this set of articles that tries to get to the true root cause of project failure.

&lt;a HREF=&quot;http://www.cleverworkarounds.com/2009/02/12/the-one-best-practice-to-rule-them-all-part-1/&quot; rel=&quot;nofollow&quot;&gt;The one best practice to rule them all - Part 1&lt;/a&gt;
&lt;a HREF=&quot;http://www.cleverworkarounds.com/2009/02/15/the-one-best-practice-to-rule-them-all-part-2/&quot; rel=&quot;nofollow&quot;&gt;The one best practice to rule them all - Part 2&lt;/a&gt;
&lt;a HREF=&quot;http://www.cleverworkarounds.com/2009/02/23/the-one-best-practice-to-rule-them-all-part-3/&quot; rel=&quot;nofollow&quot;&gt;The one best practice to rule them all - Part 3&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>This article nails it totally and goes way beyond scrum. Readers who strongly identify with this may like this set of articles that tries to get to the true root cause of project failure.</p>
<p><a HREF="http://www.cleverworkarounds.com/2009/02/12/the-one-best-practice-to-rule-them-all-part-1/" rel="nofollow">The one best practice to rule them all &#8211; Part 1</a><br />
<a HREF="http://www.cleverworkarounds.com/2009/02/15/the-one-best-practice-to-rule-them-all-part-2/" rel="nofollow">The one best practice to rule them all &#8211; Part 2</a><br />
<a HREF="http://www.cleverworkarounds.com/2009/02/23/the-one-best-practice-to-rule-them-all-part-3/" rel="nofollow">The one best practice to rule them all &#8211; Part 3</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rick Tonoli</title>
		<link>http://blog.sciodev.com/2008/11/20/agile-is-an-attitude-not-a-method/comment-page-1/#comment-11</link>
		<dc:creator>Rick Tonoli</dc:creator>
		<pubDate>Fri, 05 Dec 2008 19:18:53 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sciodev.com/?p=25#comment-11</guid>
		<description>I cannot agree more, I&#039;ve personally found that the most progress I&#039;ve made in getting teams to adopts Scrum was not when I preached the benefits of Scrum to them but rather when I encouraged and fostered a culture of open communication, ownership and pride amongst team members. Once those were in place the rest almost magically slotted in and I had no need to preach.</description>
		<content:encoded><![CDATA[<p>I cannot agree more, I&#8217;ve personally found that the most progress I&#8217;ve made in getting teams to adopts Scrum was not when I preached the benefits of Scrum to them but rather when I encouraged and fostered a culture of open communication, ownership and pride amongst team members. Once those were in place the rest almost magically slotted in and I had no need to preach.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Hogan</title>
		<link>http://blog.sciodev.com/2008/11/20/agile-is-an-attitude-not-a-method/comment-page-1/#comment-10</link>
		<dc:creator>Chris Hogan</dc:creator>
		<pubDate>Wed, 03 Dec 2008 08:35:46 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sciodev.com/?p=25#comment-10</guid>
		<description>I saw this on LinkedIn &amp; commented there, I should probably as put it here instead, so I&#039;ll repeat mysel:

Part of &quot;being agile&quot; is being flexible. Following any procedure rigidly leads to fossilization - just think what has happened to DSDM once idiots started playing games &quot;The R in RAD doesn&#039;t mean Rapid it means Right Application Development&quot; (actually said by a speaker at the DSDM conference some years ago). 

Not even good English, and the death knell for DSDM as a true agile methodology.

Agility means being able to adapt - even if it is adapting the method itself</description>
		<content:encoded><![CDATA[<p>I saw this on LinkedIn &amp; commented there, I should probably as put it here instead, so I&#8217;ll repeat mysel:</p>
<p>Part of &#8220;being agile&#8221; is being flexible. Following any procedure rigidly leads to fossilization &#8211; just think what has happened to DSDM once idiots started playing games &#8220;The R in RAD doesn&#8217;t mean Rapid it means Right Application Development&#8221; (actually said by a speaker at the DSDM conference some years ago). </p>
<p>Not even good English, and the death knell for DSDM as a true agile methodology.</p>
<p>Agility means being able to adapt &#8211; even if it is adapting the method itself</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ellen Feaheny</title>
		<link>http://blog.sciodev.com/2008/11/20/agile-is-an-attitude-not-a-method/comment-page-1/#comment-8</link>
		<dc:creator>Ellen Feaheny</dc:creator>
		<pubDate>Mon, 01 Dec 2008 18:05:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sciodev.com/?p=25#comment-8</guid>
		<description>This is a most excellent article, highly relevant to agile ways, but also to many of the issues and challenges associated with ANY product development (Waterfall OR Agile). 
In my experience, communication, accountability, and rapid delivery are always a challenge - &lt;b&gt;especially&lt;/b&gt; if you do not have the right tools (and people with right progressive attitudes to drive them).
But to the point on Agile, you fall short of spec&#039;ing the tools required to allow, ease, and proliferate Agile processes and success in organizations. 
I will be less coy, and state it flat out - since I am positive of their truth: 

 At a generic level, you need a reliable WIKI and issue tracking system, rapid build development environment, and metrics to allow the communication, constant evolution, transparency, and continual improvement evaluation of your processes/successes. 
 To take up a step, I believe solidly that &lt;a&gt;Atlassian&lt;/a&gt; provides these solutions, reliably, flexibly, and with many many integration points for progressive success (among so much else to say on this). 

Jira and Confluence WIKI already have a strong foothold in the Agile industry, but they are also GREAT &lt;b&gt;before&lt;/b&gt; you have achieved &quot;agility&quot;, allowing you to evolve and grow at your own pace.  
Further, when ready, the rest of Atlassian&#039;s product set continues to help streamline your environment (Fisheye, Bamboo), testing approaches (Clover), code reviews (Crucible), etc.  
&lt;a href=&quot;http://confluence.atlassian.com/display/ATLAS/Integration+Documentation&quot; rel=&quot;nofollow&quot;&gt;Here&#039;s a great straight-up summary of clean integration points&lt;/a&gt;.
But don&#039;t believe me - check it out for yourself - MUCH information (Webinars, testimonials, etc.) available in netland to help form your own opinion, and find your own &quot;right agile attitude&quot;.
And yes it is &quot;right attitude&quot; to &quot;get it right&quot;. Thanks for a really great &quot;reality check&quot; article Luis - well stated.</description>
		<content:encoded><![CDATA[<p>This is a most excellent article, highly relevant to agile ways, but also to many of the issues and challenges associated with ANY product development (Waterfall OR Agile).<br />
In my experience, communication, accountability, and rapid delivery are always a challenge &#8211; <b>especially</b> if you do not have the right tools (and people with right progressive attitudes to drive them).<br />
But to the point on Agile, you fall short of spec&#8217;ing the tools required to allow, ease, and proliferate Agile processes and success in organizations.<br />
I will be less coy, and state it flat out &#8211; since I am positive of their truth: </p>
<p> At a generic level, you need a reliable WIKI and issue tracking system, rapid build development environment, and metrics to allow the communication, constant evolution, transparency, and continual improvement evaluation of your processes/successes.<br />
 To take up a step, I believe solidly that <a>Atlassian</a> provides these solutions, reliably, flexibly, and with many many integration points for progressive success (among so much else to say on this). </p>
<p>Jira and Confluence WIKI already have a strong foothold in the Agile industry, but they are also GREAT <b>before</b> you have achieved &#8220;agility&#8221;, allowing you to evolve and grow at your own pace.<br />
Further, when ready, the rest of Atlassian&#8217;s product set continues to help streamline your environment (Fisheye, Bamboo), testing approaches (Clover), code reviews (Crucible), etc.<br />
<a href="http://confluence.atlassian.com/display/ATLAS/Integration+Documentation" rel="nofollow">Here&#8217;s a great straight-up summary of clean integration points</a>.<br />
But don&#8217;t believe me &#8211; check it out for yourself &#8211; MUCH information (Webinars, testimonials, etc.) available in netland to help form your own opinion, and find your own &#8220;right agile attitude&#8221;.<br />
And yes it is &#8220;right attitude&#8221; to &#8220;get it right&#8221;. Thanks for a really great &#8220;reality check&#8221; article Luis &#8211; well stated.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
