<?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: Predictability is Bad for Your Business</title>
	<atom:link href="http://theagileexecutive.com/2009/11/12/predictability-is-bad-for-your-business/feed/" rel="self" type="application/rss+xml" />
	<link>http://theagileexecutive.com/2009/11/12/predictability-is-bad-for-your-business/</link>
	<description>Making Agile Work</description>
	<lastBuildDate>Mon, 16 Jan 2012 14:09:12 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: israelgat</title>
		<link>http://theagileexecutive.com/2009/11/12/predictability-is-bad-for-your-business/#comment-749</link>
		<dc:creator><![CDATA[israelgat]]></dc:creator>
		<pubDate>Wed, 18 Nov 2009 14:35:11 +0000</pubDate>
		<guid isPermaLink="false">http://theagileexecutive.com/?p=3515#comment-749</guid>
		<description><![CDATA[I would actually characterize the phenomenon as violation of the Agile Triangle (as distinct from the Agile Iron Triangle). The key concept to bear in mind is &lt;strong&gt;value over constraints&lt;/strong&gt;. See Figure 1.3 in the July 2009 edition of Jim Highsmith&#039;s &lt;a href=&quot;http://www.amazon.com/gp/product/0321658396/ref=s9_simz_gw_s0_p14_i1?pf_rd_m=ATVPDKIKX0DER&amp;pf_rd_s=center-3&amp;pf_rd_r=1BMMG3HC05Z0RD0D4H0S&amp;pf_rd_t=101&amp;pf_rd_p=470938811&amp;pf_rd_i=507846&quot; rel=&quot;nofollow&quot;&gt;Agile Project Management: Creating Innovative Products&lt;/a&gt; for the evolution of the thinking:

&lt;blockquote&gt;Traditional Iron Triangle --&gt; Agile Iron Triangle --&gt; Agile Triangle&lt;/blockquote&gt;

Israel ]]></description>
		<content:encoded><![CDATA[<p>I would actually characterize the phenomenon as violation of the Agile Triangle (as distinct from the Agile Iron Triangle). The key concept to bear in mind is <strong>value over constraints</strong>. See Figure 1.3 in the July 2009 edition of Jim Highsmith&#8217;s <a href="http://www.amazon.com/gp/product/0321658396/ref=s9_simz_gw_s0_p14_i1?pf_rd_m=ATVPDKIKX0DER&amp;pf_rd_s=center-3&amp;pf_rd_r=1BMMG3HC05Z0RD0D4H0S&amp;pf_rd_t=101&amp;pf_rd_p=470938811&amp;pf_rd_i=507846" rel="nofollow">Agile Project Management: Creating Innovative Products</a> for the evolution of the thinking:</p>
<blockquote><p>Traditional Iron Triangle &#8211;&gt; Agile Iron Triangle &#8211;&gt; Agile Triangle</p></blockquote>
<p>Israel</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Lunt</title>
		<link>http://theagileexecutive.com/2009/11/12/predictability-is-bad-for-your-business/#comment-748</link>
		<dc:creator><![CDATA[Mike Lunt]]></dc:creator>
		<pubDate>Tue, 17 Nov 2009 18:38:21 +0000</pubDate>
		<guid isPermaLink="false">http://theagileexecutive.com/?p=3515#comment-748</guid>
		<description><![CDATA[I believe Google solves some of this problem with their 20 percent time, and others have solved this by creating separate incubator groups.

Having been in Agile shops for a while, I have come to believe &quot;reliable delivery&quot; is a form of predictability for an engineering team.  In the case you mentioned, I assume you are referring to a violation of the Iron Triangle.]]></description>
		<content:encoded><![CDATA[<p>I believe Google solves some of this problem with their 20 percent time, and others have solved this by creating separate incubator groups.</p>
<p>Having been in Agile shops for a while, I have come to believe &#8220;reliable delivery&#8221; is a form of predictability for an engineering team.  In the case you mentioned, I assume you are referring to a violation of the Iron Triangle.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

