<?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: The Name of the Game is Change</title>
	<atom:link href="http://www.pavley.com/2009/10/14/the-name-of-the-game-is-change/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pavley.com/2009/10/14/the-name-of-the-game-is-change/</link>
	<description>“A great leap in the dark” – Thomas Hobbes</description>
	<lastBuildDate>Fri, 30 Dec 2011 13:42:18 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: pav</title>
		<link>http://www.pavley.com/2009/10/14/the-name-of-the-game-is-change/comment-page-1/#comment-125</link>
		<dc:creator>pav</dc:creator>
		<pubDate>Mon, 02 Nov 2009 01:16:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.pavley.com/?p=89#comment-125</guid>
		<description>Thanks for the comment Anish. I agree with you: You have to be really organized before you can be successful with Agile and Scrum.</description>
		<content:encoded><![CDATA[<p>Thanks for the comment Anish. I agree with you: You have to be really organized before you can be successful with Agile and Scrum.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pav</title>
		<link>http://www.pavley.com/2009/10/14/the-name-of-the-game-is-change/comment-page-1/#comment-118</link>
		<dc:creator>pav</dc:creator>
		<pubDate>Fri, 30 Oct 2009 13:04:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.pavley.com/?p=89#comment-118</guid>
		<description>Excellent comments James and Andrey! Ever since I first ran into the Model-View-Controller design pattern  I released that layering biz logic was an amazingly powerful tool to deal with changing requirements. Agile is just he methodology that lets you do it with people :)</description>
		<content:encoded><![CDATA[<p>Excellent comments James and Andrey! Ever since I first ran into the Model-View-Controller design pattern  I released that layering biz logic was an amazingly powerful tool to deal with changing requirements. Agile is just he methodology that lets you do it with people <img src='http://www.pavley.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrey Fedorov</title>
		<link>http://www.pavley.com/2009/10/14/the-name-of-the-game-is-change/comment-page-1/#comment-106</link>
		<dc:creator>Andrey Fedorov</dc:creator>
		<pubDate>Tue, 20 Oct 2009 23:30:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.pavley.com/?p=89#comment-106</guid>
		<description>&quot;JIT planning&quot; is spot on, and most important. I&#039;ve heard &lt;a href=&quot;http://en.wikipedia.org/wiki/Alan_Kay&quot; rel=&quot;nofollow&quot;&gt;famous software people&lt;/a&gt; refer to this as &quot;late binding&quot; or as the &lt;i&gt;Open Future Principle&lt;/i&gt;: “The best way to implement the future is to avoid having to predict it” (&lt;a href=&quot;http://www.vpri.org/pdf/rn2006001a_colaswp.pdf&quot; rel=&quot;nofollow&quot;&gt;pdf&lt;/a&gt;). In other words, don&#039;t make decisions now if you can make them later (when you&#039;ll have more data). 

This, in turn, yields a very important architectural axiom - that we ought to choose and create systems which allow you to defer decisions to a later point. This means choosing systems which let you separate business logic to make it reusable over those that don&#039;t, picking systems which allow you to change garbage collection strategies over those which don&#039;t, and systems which allow you to separate your domain objects from their serialization strategies.</description>
		<content:encoded><![CDATA[<p>&#8220;JIT planning&#8221; is spot on, and most important. I&#8217;ve heard <a href="http://en.wikipedia.org/wiki/Alan_Kay" rel="nofollow">famous software people</a> refer to this as &#8220;late binding&#8221; or as the <i>Open Future Principle</i>: “The best way to implement the future is to avoid having to predict it” (<a href="http://www.vpri.org/pdf/rn2006001a_colaswp.pdf" rel="nofollow">pdf</a>). In other words, don&#8217;t make decisions now if you can make them later (when you&#8217;ll have more data). </p>
<p>This, in turn, yields a very important architectural axiom &#8211; that we ought to choose and create systems which allow you to defer decisions to a later point. This means choosing systems which let you separate business logic to make it reusable over those that don&#8217;t, picking systems which allow you to change garbage collection strategies over those which don&#8217;t, and systems which allow you to separate your domain objects from their serialization strategies.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anish</title>
		<link>http://www.pavley.com/2009/10/14/the-name-of-the-game-is-change/comment-page-1/#comment-104</link>
		<dc:creator>Anish</dc:creator>
		<pubDate>Tue, 20 Oct 2009 02:45:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.pavley.com/?p=89#comment-104</guid>
		<description>&quot;This is in well run organizations. In poorly run organizations the change is constant and internally generated&quot; - Very well said! This emphsizes a need to be organized and in control when implementing agile principals. I feel it&#039;s an important point that is many times missed in following scrum. Thanks John

Anish B</description>
		<content:encoded><![CDATA[<p>&#8220;This is in well run organizations. In poorly run organizations the change is constant and internally generated&#8221; &#8211; Very well said! This emphsizes a need to be organized and in control when implementing agile principals. I feel it&#8217;s an important point that is many times missed in following scrum. Thanks John</p>
<p>Anish B</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James</title>
		<link>http://www.pavley.com/2009/10/14/the-name-of-the-game-is-change/comment-page-1/#comment-82</link>
		<dc:creator>James</dc:creator>
		<pubDate>Thu, 15 Oct 2009 01:01:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.pavley.com/?p=89#comment-82</guid>
		<description>Another really great piece.  I wrote an article published in Innovation in 2001 on a process I call &quot;Channeling Innovation&quot; that encourages, accommodates, and manages change.  The &quot;five patterns&quot; you list fold neatly into it.  I&#039;m looking forward to your next post.</description>
		<content:encoded><![CDATA[<p>Another really great piece.  I wrote an article published in Innovation in 2001 on a process I call &#8220;Channeling Innovation&#8221; that encourages, accommodates, and manages change.  The &#8220;five patterns&#8221; you list fold neatly into it.  I&#8217;m looking forward to your next post.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

