<?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 for Social Complexity and Agility</title>
	<atom:link href="http://www.metaprog.com/blogs/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.metaprog.com/blogs</link>
	<description>Joseph Pelrine&#039;s weblog</description>
	<lastBuildDate>Mon, 02 Aug 2010 10:02:37 +0200</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on log(N) = 0.093 + 3.389 log(CR) (1) (r2=0.764, t34=10.35, p by keith</title>
		<link>http://www.metaprog.com/blogs/2009/01/logn-0093-3389-logcr-1-r20764-t341035-p/comment-page-1/#comment-20</link>
		<dc:creator>keith</dc:creator>
		<pubDate>Thu, 18 Feb 2010 22:01:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.metaprog.com/blogs/?p=7#comment-20</guid>
		<description>So, isn&#039;t there a contraction here with the way that Scrum is marketed by its various competing pyramid schemes?

Scrum marketers talk a good game about development projects being on &quot;the edge of chaos&quot; on the Stacey Matrix, which agrees well with the Cynefin domain of the Complex, where retrospective coherence lives. Yet the sales force deliver Certification courses as if Scrum were Best Practice, which belongs in the domain of the Simple. I am at a loss to understand how an ossified process prescription from 1995 of ideas based on an article from 1986 can be an exemplar of the &quot;Probe-Sense-Response&quot; approach.

That doesn&#039;t mean that Scrum is a bad way to run a project, necessarily, just that that it seems to have a contradiction at its heart.</description>
		<content:encoded><![CDATA[<p>So, isn&#8217;t there a contraction here with the way that Scrum is marketed by its various competing pyramid schemes?</p>
<p>Scrum marketers talk a good game about development projects being on &#8220;the edge of chaos&#8221; on the Stacey Matrix, which agrees well with the Cynefin domain of the Complex, where retrospective coherence lives. Yet the sales force deliver Certification courses as if Scrum were Best Practice, which belongs in the domain of the Simple. I am at a loss to understand how an ossified process prescription from 1995 of ideas based on an article from 1986 can be an exemplar of the &#8220;Probe-Sense-Response&#8221; approach.</p>
<p>That doesn&#8217;t mean that Scrum is a bad way to run a project, necessarily, just that that it seems to have a contradiction at its heart.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The relationship between XP and Scrum project variables by Fidelity &#8211; The Lost Dimension of the Iron Triangle &#171; AvailAgility</title>
		<link>http://www.metaprog.com/blogs/2009/06/the-relationship-between-xp-and-scrum-project-variables/comment-page-1/#comment-18</link>
		<dc:creator>Fidelity &#8211; The Lost Dimension of the Iron Triangle &#171; AvailAgility</dc:creator>
		<pubDate>Wed, 30 Dec 2009 11:27:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.metaprog.com/blogs/?p=58#comment-18</guid>
		<description>[...] Axis is Scope, and the burndown slope is a function of cost and time. Keith Braithwaite and Joseph Pelrine both blogged about this after a conversation we had in Zurich earlier this year. I like to add a [...]</description>
		<content:encoded><![CDATA[<p>[...] Axis is Scope, and the burndown slope is a function of cost and time. Keith Braithwaite and Joseph Pelrine both blogged about this after a conversation we had in Zurich earlier this year. I like to add a [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on log(N) = 0.093 + 3.389 log(CR) (1) (r2=0.764, t34=10.35, p by admin</title>
		<link>http://www.metaprog.com/blogs/2009/01/logn-0093-3389-logcr-1-r20764-t341035-p/comment-page-1/#comment-17</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Sun, 13 Dec 2009 13:39:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.metaprog.com/blogs/?p=7#comment-17</guid>
		<description>Great article :)</description>
		<content:encoded><![CDATA[<p>Great article <img src='http://www.metaprog.com/blogs/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Turning up the heat &#8211; the levels by About the Munich Scrum Gathering - pt. 2 at Ricardo Mestre&#8217;s Blog</title>
		<link>http://www.metaprog.com/blogs/2009/07/turning-up-the-heat-the-levels/comment-page-1/#comment-15</link>
		<dc:creator>About the Munich Scrum Gathering - pt. 2 at Ricardo Mestre&#8217;s Blog</dc:creator>
		<pubDate>Sun, 08 Nov 2009 00:53:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.metaprog.com/blogs/?p=74#comment-15</guid>
		<description>[...] Enter the Scrum Master&#8217;s role: when energy is applied to this System (and here System=Team+Tools+History of the SW previously developed), the System will move into several states of Self-Organization. Take into consideration that: a) Self-Organization is a disruptive state (in the sense that it disrupts Self-Assembly, i.e. the pre-determined behaviour, before any energy was applied) and b) it&#8217;s a non-equilibrium state that will decay back to Self-Assembly. And this is exactly why the Scrum Master&#8217;s job of keeping a Team on a high productity state is a work that&#8217;s never done. If you remove the energy, the Team will decay into Self-Assembly, into the &#8220;old ways&#8221; and will become a Group. And exactly how much energy shall be then applied? Joseph Pelrine explains it in a very clear way on his blog: part 1 here and part 2 here. [...]</description>
		<content:encoded><![CDATA[<p>[...] Enter the Scrum Master&#8217;s role: when energy is applied to this System (and here System=Team+Tools+History of the SW previously developed), the System will move into several states of Self-Organization. Take into consideration that: a) Self-Organization is a disruptive state (in the sense that it disrupts Self-Assembly, i.e. the pre-determined behaviour, before any energy was applied) and b) it&#8217;s a non-equilibrium state that will decay back to Self-Assembly. And this is exactly why the Scrum Master&#8217;s job of keeping a Team on a high productity state is a work that&#8217;s never done. If you remove the energy, the Team will decay into Self-Assembly, into the &#8220;old ways&#8221; and will become a Group. And exactly how much energy shall be then applied? Joseph Pelrine explains it in a very clear way on his blog: part 1 here and part 2 here. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Turning up the heat &#8211; the basic model by About the Munich Scrum Gathering - pt. 2 at Ricardo Mestre&#8217;s Blog</title>
		<link>http://www.metaprog.com/blogs/2009/06/turning-up-the-heat-the-basic-model/comment-page-1/#comment-14</link>
		<dc:creator>About the Munich Scrum Gathering - pt. 2 at Ricardo Mestre&#8217;s Blog</dc:creator>
		<pubDate>Sun, 08 Nov 2009 00:52:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.metaprog.com/blogs/?p=65#comment-14</guid>
		<description>[...] how much energy shall be then applied? Joseph Pelrine explains it in a very clear way on his blog: part 1 here and part 2 [...]</description>
		<content:encoded><![CDATA[<p>[...] how much energy shall be then applied? Joseph Pelrine explains it in a very clear way on his blog: part 1 here and part 2 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Turning up the heat &#8211; the basic model by admin</title>
		<link>http://www.metaprog.com/blogs/2009/06/turning-up-the-heat-the-basic-model/comment-page-1/#comment-13</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Fri, 06 Nov 2009 17:14:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.metaprog.com/blogs/?p=65#comment-13</guid>
		<description>Any suggestions? I&#039;ve been researching this stuff since before the &quot;Agile&quot; term was applied to it, so I have no problem with using another name. Nevertheless, &quot;Agile&quot; is a term that most people will recognize, even if their reaction is the same as yours...</description>
		<content:encoded><![CDATA[<p>Any suggestions? I&#8217;ve been researching this stuff since before the &#8220;Agile&#8221; term was applied to it, so I have no problem with using another name. Nevertheless, &#8220;Agile&#8221; is a term that most people will recognize, even if their reaction is the same as yours&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Turning up the heat &#8211; the basic model by pierg</title>
		<link>http://www.metaprog.com/blogs/2009/06/turning-up-the-heat-the-basic-model/comment-page-1/#comment-12</link>
		<dc:creator>pierg</dc:creator>
		<pubDate>Fri, 06 Nov 2009 14:11:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.metaprog.com/blogs/?p=65#comment-12</guid>
		<description>No please!! Don&#039;t put the &#039;Agile&#039; word in it ... we are so bored of this new buzz word! I&#039;m sure you can get something original!
PierG
http://pierg.wordpress.com</description>
		<content:encoded><![CDATA[<p>No please!! Don&#8217;t put the &#8216;Agile&#8217; word in it &#8230; we are so bored of this new buzz word! I&#8217;m sure you can get something original!<br />
PierG<br />
<a href="http://pierg.wordpress.com" rel="nofollow">http://pierg.wordpress.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on On retrospective coherence &#8211; Part 1 by uberVU - social comments</title>
		<link>http://www.metaprog.com/blogs/2009/10/on-retrospective-coherence-part-1/comment-page-1/#comment-11</link>
		<dc:creator>uberVU - social comments</dc:creator>
		<pubDate>Tue, 27 Oct 2009 22:02:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.metaprog.com/blogs/?p=78#comment-11</guid>
		<description>&lt;strong&gt;Social comments and analytics for this post...&lt;/strong&gt;

This post was mentioned on Twitter by josephpelrine: New book excerpt: on retrospective coherence - part 1 http://tr.im/DfhD...</description>
		<content:encoded><![CDATA[<p><strong>Social comments and analytics for this post&#8230;</strong></p>
<p>This post was mentioned on Twitter by josephpelrine: New book excerpt: on retrospective coherence &#8211; part 1 <a href="http://tr.im/DfhD..." rel="nofollow">http://tr.im/DfhD&#8230;</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on On retrospective coherence &#8211; Part 1 by Tweets that mention Complex and Agile » On retrospective coherence – Part 1 -- Topsy.com</title>
		<link>http://www.metaprog.com/blogs/2009/10/on-retrospective-coherence-part-1/comment-page-1/#comment-10</link>
		<dc:creator>Tweets that mention Complex and Agile » On retrospective coherence – Part 1 -- Topsy.com</dc:creator>
		<pubDate>Tue, 27 Oct 2009 18:50:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.metaprog.com/blogs/?p=78#comment-10</guid>
		<description>[...] This post was mentioned on Twitter by Marc Evers, Joseph Pelrine. Joseph Pelrine said: New book excerpt: on retrospective coherence - part 1 http://tr.im/DfhD [...]</description>
		<content:encoded><![CDATA[<p>[...] This post was mentioned on Twitter by Marc Evers, Joseph Pelrine. Joseph Pelrine said: New book excerpt: on retrospective coherence &#8211; part 1 <a href="http://tr.im/DfhD" rel="nofollow">http://tr.im/DfhD</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Turning up the heat &#8211; the levels by Guiding a Self Organising Team into Effeciency &#124; Wildfalcon</title>
		<link>http://www.metaprog.com/blogs/2009/07/turning-up-the-heat-the-levels/comment-page-1/#comment-9</link>
		<dc:creator>Guiding a Self Organising Team into Effeciency &#124; Wildfalcon</dc:creator>
		<pubDate>Fri, 23 Oct 2009 15:21:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.metaprog.com/blogs/?p=74#comment-9</guid>
		<description>[...] were also a couple of ideas how teams change and evolve over time. You should cook a team, but not burn them, as well as the classic,  Storming Forming Norming and [...]</description>
		<content:encoded><![CDATA[<p>[...] were also a couple of ideas how teams change and evolve over time. You should cook a team, but not burn them, as well as the classic,  Storming Forming Norming and [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
