<?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"
	>
<channel>
	<title>Comments for Scaling Software Agility</title>
	<atom:link href="http://scalingsoftwareagility.wordpress.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://scalingsoftwareagility.wordpress.com</link>
	<description>Best Practices for Large Enterprises, by Dean Leffingwell</description>
	<pubDate>Sun, 20 Jul 2008 17:01:22 +0000</pubDate>
	<generator>http://wordpress.org/?v=MU</generator>
		<item>
		<title>Comment on On Agile Maturity and Hardening Iterations by Enterprise Agility–The Big Picture (2): Iterations &#171; Scaling Software Agility</title>
		<link>http://scalingsoftwareagility.wordpress.com/2008/03/21/on-agile-maturity-and-hardening-iterations/#comment-1245</link>
		<dc:creator>Enterprise Agility–The Big Picture (2): Iterations &#171; Scaling Software Agility</dc:creator>
		<pubDate>Thu, 17 Jul 2008 07:06:44 +0000</pubDate>
		<guid isPermaLink="false">http://scalingsoftwareagility.wordpress.com/2008/03/21/on-agile-maturity-and-hardening-iterations/#comment-1245</guid>
		<description>[...] we&#8217;ve illustrated four development iterations (indicated by a full iteration backlog) and one hardening iteration (indicated by an empty backlog). This is somewhat arbitrary as well and there is no fixed rule for [...]</description>
		<content:encoded><![CDATA[<p>[...] we&#8217;ve illustrated four development iterations (indicated by a full iteration backlog) and one hardening iteration (indicated by an empty backlog). This is somewhat arbitrary as well and there is no fixed rule for [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Enterprise Agility–The Big Picture by Enterprise Agility–The Big Picture (2): Iterations &#171; Scaling Software Agility</title>
		<link>http://scalingsoftwareagility.wordpress.com/2008/07/12/enterprise-agility%e2%80%93the-big-picture/#comment-1244</link>
		<dc:creator>Enterprise Agility–The Big Picture (2): Iterations &#171; Scaling Software Agility</dc:creator>
		<pubDate>Thu, 17 Jul 2008 07:05:10 +0000</pubDate>
		<guid isPermaLink="false">http://scalingsoftwareagility.wordpress.com/2008/07/12/enterprise-agility%e2%80%93the-big-picture/#comment-1244</guid>
		<description>[...] Big Picture (2):&#160;Iterations  Posted on July 17, 2008 by Dean Leffingwell   Note: In the post Enterprise Agility: The Big Picture, we introduced an overview graphic intended to capture the essence of enterprise agility and the [...]</description>
		<content:encoded><![CDATA[<p>[...] Big Picture (2):&nbsp;Iterations  Posted on July 17, 2008 by Dean Leffingwell   Note: In the post Enterprise Agility: The Big Picture, we introduced an overview graphic intended to capture the essence of enterprise agility and the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Failing “soft” is an Option in Agile by Enterprise Agility–The Big Picture (2): Iterations &#171; Scaling Software Agility</title>
		<link>http://scalingsoftwareagility.wordpress.com/2008/06/23/failing-%e2%80%9csoft%e2%80%9d-is-an-option/#comment-1243</link>
		<dc:creator>Enterprise Agility–The Big Picture (2): Iterations &#171; Scaling Software Agility</dc:creator>
		<pubDate>Thu, 17 Jul 2008 07:00:58 +0000</pubDate>
		<guid isPermaLink="false">http://scalingsoftwareagility.wordpress.com/2008/06/23/failing-%e2%80%9csoft%e2%80%9d-is-an-option/#comment-1243</guid>
		<description>[...] being built in one week iterations). Four weeks or one month is simply too long, as there are not enough times to fail before some major release commitment. In other words, the lessons learned are too far apart to make [...]</description>
		<content:encoded><![CDATA[<p>[...] being built in one week iterations). Four weeks or one month is simply too long, as there are not enough times to fail before some major release commitment. In other words, the lessons learned are too far apart to make [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Enterprise Agility–The Big Picture by Enterprise Agility–The Big Picture (1): Teams &#171; Scaling Software Agility</title>
		<link>http://scalingsoftwareagility.wordpress.com/2008/07/12/enterprise-agility%e2%80%93the-big-picture/#comment-1242</link>
		<dc:creator>Enterprise Agility–The Big Picture (1): Teams &#171; Scaling Software Agility</dc:creator>
		<pubDate>Tue, 15 Jul 2008 07:14:14 +0000</pubDate>
		<guid isPermaLink="false">http://scalingsoftwareagility.wordpress.com/2008/07/12/enterprise-agility%e2%80%93the-big-picture/#comment-1242</guid>
		<description>[...] Big Picture (1):&#160;Teams  Posted on July 15, 2008 by Dean Leffingwell   Note: In the post Enterprise Agility-The Big Picture, we introduced an overview graphic intended to capture the essence of enterprise agility and the [...]</description>
		<content:encoded><![CDATA[<p>[...] Big Picture (1):&nbsp;Teams  Posted on July 15, 2008 by Dean Leffingwell   Note: In the post Enterprise Agility-The Big Picture, we introduced an overview graphic intended to capture the essence of enterprise agility and the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Newly Released Quantitative Data on Enterprise Agility Benefits at BMC Software by Agile Executive - Final, Six Part BMC Executive Interview Now On Line &#171; Scaling Software Agility</title>
		<link>http://scalingsoftwareagility.wordpress.com/2007/09/21/newly-release-quantitative-data-on-enterprise-agility-benefits-at-bmc-software/#comment-1232</link>
		<dc:creator>Agile Executive - Final, Six Part BMC Executive Interview Now On Line &#171; Scaling Software Agility</dc:creator>
		<pubDate>Wed, 09 Jul 2008 15:19:36 +0000</pubDate>
		<guid isPermaLink="false">http://scalingsoftwareagility.wordpress.com/2007/09/21/newly-release-quantitative-data-on-enterprise-agility-benefits-at-bmc-software/#comment-1232</guid>
		<description>[...] by Dean Leffingwell   Israel Gat (BMC VP) has just completed a six part interview series on the BMC agile transformation experience at the Agile Thinkers blog. This series is an open, honest and direct perspective from an [...]</description>
		<content:encoded><![CDATA[<p>[...] by Dean Leffingwell   Israel Gat (BMC VP) has just completed a six part interview series on the BMC agile transformation experience at the Agile Thinkers blog. This series is an open, honest and direct perspective from an [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Requisite Virtues of the Agile Executive by David Wood</title>
		<link>http://scalingsoftwareagility.wordpress.com/2008/07/01/requisite-virtues-of-the-agile-executive/#comment-1224</link>
		<dc:creator>David Wood</dc:creator>
		<pubDate>Tue, 01 Jul 2008 15:02:01 +0000</pubDate>
		<guid isPermaLink="false">http://scalingsoftwareagility.wordpress.com/2008/07/01/requisite-virtues-of-the-agile-executive/#comment-1224</guid>
		<description>&lt;i&gt;“The wise man knows how not to get into a ditch that the smart man knows how to get out of.”&lt;/i&gt;

Brilliant!  Another definition of wisdom, that I like, is that being wise means being aware of the areas where you're probably lacking knowledge (and so you'll take more care), whereas being clever means being driven by knowledge without due acknowledgement of possible gaps in knowledge.</description>
		<content:encoded><![CDATA[<p><i>“The wise man knows how not to get into a ditch that the smart man knows how to get out of.”</i></p>
<p>Brilliant!  Another definition of wisdom, that I like, is that being wise means being aware of the areas where you&#8217;re probably lacking knowledge (and so you&#8217;ll take more care), whereas being clever means being driven by knowledge without due acknowledgement of possible gaps in knowledge.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Requisite Virtues of the Agile Executive by Israel</title>
		<link>http://scalingsoftwareagility.wordpress.com/2008/07/01/requisite-virtues-of-the-agile-executive/#comment-1223</link>
		<dc:creator>Israel</dc:creator>
		<pubDate>Tue, 01 Jul 2008 12:36:31 +0000</pubDate>
		<guid isPermaLink="false">http://scalingsoftwareagility.wordpress.com/2008/07/01/requisite-virtues-of-the-agile-executive/#comment-1223</guid>
		<description>To Dean's question about "wisdom of life", I would suggest a Hebrew proverb as a quick answer:

"The wise man knows how not to get into a ditch that the smart man knows how to get out of."</description>
		<content:encoded><![CDATA[<p>To Dean&#8217;s question about &#8220;wisdom of life&#8221;, I would suggest a Hebrew proverb as a quick answer:</p>
<p>&#8220;The wise man knows how not to get into a ditch that the smart man knows how to get out of.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Requisite Virtues of the Agile Executive by Israel</title>
		<link>http://scalingsoftwareagility.wordpress.com/2008/07/01/requisite-virtues-of-the-agile-executive/#comment-1222</link>
		<dc:creator>Israel</dc:creator>
		<pubDate>Tue, 01 Jul 2008 12:27:51 +0000</pubDate>
		<guid isPermaLink="false">http://scalingsoftwareagility.wordpress.com/2008/07/01/requisite-virtues-of-the-agile-executive/#comment-1222</guid>
		<description>IMHO the need for control (or to be more precise the illusion of control) is the number one obstacle to implementing Agile. My counsel to executives who consider doing Agile is very simple:

"Think once, think twice, think thrice whether you are really, really, really ready to empower in the full sense of the word.  Empowerment is like an acid test – for better or worse it will give you your defining  moments."</description>
		<content:encoded><![CDATA[<p>IMHO the need for control (or to be more precise the illusion of control) is the number one obstacle to implementing Agile. My counsel to executives who consider doing Agile is very simple:</p>
<p>&#8220;Think once, think twice, think thrice whether you are really, really, really ready to empower in the full sense of the word.  Empowerment is like an acid test – for better or worse it will give you your defining  moments.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The New New Product Development Game and the Roots of Scrum by Harnessing Innovation: Lightweight Governance Models for High Performing Agile teams &#171; Scaling Software Agility</title>
		<link>http://scalingsoftwareagility.wordpress.com/2008/06/05/the-new-new-product-development-game-and-the-roots-of-scrum/#comment-1215</link>
		<dc:creator>Harnessing Innovation: Lightweight Governance Models for High Performing Agile teams &#171; Scaling Software Agility</dc:creator>
		<pubDate>Wed, 25 Jun 2008 15:17:36 +0000</pubDate>
		<guid isPermaLink="false">http://scalingsoftwareagility.wordpress.com/?p=185#comment-1215</guid>
		<description>[...] Note (1): this seminal article in the Harvard Business Review in 1986 is the best article I&#8217;ve ever seen on the principles and practices of concurrent engineering from the Toyota perspective, and is further described in the post The New New Product Development Game and the Roots of Scrum. Also see the post: http://scalingsoftwareagility.wordpress.com/2008/06/05/the-new-new-product-development-game-and-the-.... [...]</description>
		<content:encoded><![CDATA[<p>[...] Note (1): this seminal article in the Harvard Business Review in 1986 is the best article I&#8217;ve ever seen on the principles and practices of concurrent engineering from the Toyota perspective, and is further described in the post The New New Product Development Game and the Roots of Scrum. Also see the post: <a href="http://scalingsoftwareagility.wordpress.com/2008/06/05/the-new-new-product-development-game-and-the-..." rel="nofollow">http://scalingsoftwareagility.wordpress.com/2008/06/05/the-new-new-product-development-game-and-the-&#8230;</a>. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Agile Architecture Principle #5 – The bigger the system, the longer the runway by Principle #7 – There is no monopoly on innovation &#171; Scaling Software Agility</title>
		<link>http://scalingsoftwareagility.wordpress.com/2008/04/29/agile-architecture-principle-5-%e2%80%93-the-bigger-the-airship-the-longer-the-runway/#comment-1197</link>
		<dc:creator>Principle #7 – There is no monopoly on innovation &#171; Scaling Software Agility</dc:creator>
		<pubDate>Thu, 22 May 2008 16:37:32 +0000</pubDate>
		<guid isPermaLink="false">http://scalingsoftwareagility.wordpress.com/?p=169#comment-1197</guid>
		<description>[...] an earlier principle, the bigger the system, the longer the runway, we described the need for teams to have sufficient architectural runway to be able to reliably [...]</description>
		<content:encoded><![CDATA[<p>[...] an earlier principle, the bigger the system, the longer the runway, we described the need for teams to have sufficient architectural runway to be able to reliably [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
