<?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: Turning up the heat &#8211; the levels</title>
	<atom:link href="http://www.metaprog.com/blogs/2009/07/turning-up-the-heat-the-levels/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.metaprog.com/blogs/2009/07/turning-up-the-heat-the-levels/</link>
	<description>Joseph Pelrine&#039;s weblog</description>
	<lastBuildDate>Mon, 03 Oct 2011 09:23:04 +0200</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>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>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>

