<?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 Dreamfeed</title>
	<atom:link href="http://blog.piecemealgrowth.net/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.piecemealgrowth.net</link>
	<description>Marc's weblog</description>
	<lastBuildDate>Wed, 14 Oct 2009 15:31:45 +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 Systems thinking with diagrams of effects by Len MAlczynski</title>
		<link>http://blog.piecemealgrowth.net/systems-thinking-with-diagrams-of-effects/comment-page-1/#comment-16824</link>
		<dc:creator>Len MAlczynski</dc:creator>
		<pubDate>Wed, 14 Oct 2009 15:31:45 +0000</pubDate>
		<guid isPermaLink="false">http://blog.piecemealgrowth.net/?p=268#comment-16824</guid>
		<description>A few more references:
James D. Hart, Discovering Dynamics in Software Engineering
Tarek Abdel-Hamid and Stuart Madnick, Software Project Dynamics 
and one I have not read yet
Raymond Madachy, Software Process Dynamics</description>
		<content:encoded><![CDATA[<p>A few more references:<br />
James D. Hart, Discovering Dynamics in Software Engineering<br />
Tarek Abdel-Hamid and Stuart Madnick, Software Project Dynamics<br />
and one I have not read yet<br />
Raymond Madachy, Software Process Dynamics</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Conference appearences in October by Fall Conference Appearances at me.andering &#8211; Willem van den Ende</title>
		<link>http://blog.piecemealgrowth.net/conference-appearences-in-october/comment-page-1/#comment-16725</link>
		<dc:creator>Fall Conference Appearances at me.andering &#8211; Willem van den Ende</dc:creator>
		<pubDate>Fri, 09 Oct 2009 10:53:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.piecemealgrowth.net/?p=252#comment-16725</guid>
		<description>[...]   First up is Scan-Agile next Thursday and Friday in Helsinki, Finland. Marc already wrote about our Story Testing workshop.  I&#8217;m also very much looking forward to participating in the Scan-Agile Open Space, [...]</description>
		<content:encoded><![CDATA[<p>[...]   First up is Scan-Agile next Thursday and Friday in Helsinki, Finland. Marc already wrote about our Story Testing workshop.  I&#8217;m also very much looking forward to participating in the Scan-Agile Open Space, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Agile Open Holland 2009 by Come defend &#8216;your named cloud&#8217; at Agile Open Holland at me.andering</title>
		<link>http://blog.piecemealgrowth.net/agile-open-holland-2009/comment-page-1/#comment-14812</link>
		<dc:creator>Come defend &#8216;your named cloud&#8217; at Agile Open Holland at me.andering</dc:creator>
		<pubDate>Tue, 07 Jul 2009 23:42:45 +0000</pubDate>
		<guid isPermaLink="false">http://blog.piecemealgrowth.net/?p=203#comment-14812</guid>
		<description>[...] already has the scoop, details and a pretty word cloud to explain the theme, so I&#8217;ll keep it short and simple. The next Agile Open conference in the Netherlands will be [...]</description>
		<content:encoded><![CDATA[<p>[...] already has the scoop, details and a pretty word cloud to explain the theme, so I&#8217;ll keep it short and simple. The next Agile Open conference in the Netherlands will be [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Principles of time management by Geena Murphy</title>
		<link>http://blog.piecemealgrowth.net/principles-of-time-management/comment-page-1/#comment-13277</link>
		<dc:creator>Geena Murphy</dc:creator>
		<pubDate>Wed, 20 May 2009 11:49:37 +0000</pubDate>
		<guid isPermaLink="false">http://blog.piecemealgrowth.net/?p=106#comment-13277</guid>
		<description>I must say great article and well thought of as some time management articles are the same  but this was a good solid read!</description>
		<content:encoded><![CDATA[<p>I must say great article and well thought of as some time management articles are the same  but this was a good solid read!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Risk Analysis by Scenario Planning, an illusion that works &#171; Serendipity</title>
		<link>http://blog.piecemealgrowth.net/riskanalysishtml/comment-page-1/#comment-12516</link>
		<dc:creator>Scenario Planning, an illusion that works &#171; Serendipity</dc:creator>
		<pubDate>Tue, 07 Apr 2009 13:23:54 +0000</pubDate>
		<guid isPermaLink="false">http://test.piecemealgrowth.net/riskanalysishtml/#comment-12516</guid>
		<description>[...] here 4 - Anticipating - we establish routines based on our past experience with them; e.g. explicit risk management activities that help to anticipate or prevent troubles instead of reacting to the troubles when they [...]</description>
		<content:encoded><![CDATA[<p>[...] here 4 &#8211; Anticipating &#8211; we establish routines based on our past experience with them; e.g. explicit risk management activities that help to anticipate or prevent troubles instead of reacting to the troubles when they [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Cultural Patterns of Software Organizations by Scenario Planning, an illusion that works &#171; Serendipity</title>
		<link>http://blog.piecemealgrowth.net/cultural-patterns-of-software-organizations/comment-page-1/#comment-12515</link>
		<dc:creator>Scenario Planning, an illusion that works &#171; Serendipity</dc:creator>
		<pubDate>Tue, 07 Apr 2009 13:22:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.piecemealgrowth.net/cultural-patterns-of-software-organizations/#comment-12515</guid>
		<description>[...] Planning, an illusion that&#160;works  Marc wrote, and I am jumping ahead some here 4 - Anticipating - we establish routines based on our past [...]</description>
		<content:encoded><![CDATA[<p>[...] Planning, an illusion that&nbsp;works  Marc wrote, and I am jumping ahead some here 4 &#8211; Anticipating &#8211; we establish routines based on our past [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Risk Analysis by Scenario Planning is an Illusion &#171; Serendipity</title>
		<link>http://blog.piecemealgrowth.net/riskanalysishtml/comment-page-1/#comment-12514</link>
		<dc:creator>Scenario Planning is an Illusion &#171; Serendipity</dc:creator>
		<pubDate>Tue, 07 Apr 2009 13:20:18 +0000</pubDate>
		<guid isPermaLink="false">http://test.piecemealgrowth.net/riskanalysishtml/#comment-12514</guid>
		<description>[...] here 4 - Anticipating - we establish routines based on our past experience with them; e.g. explicit risk management activities that help to anticipate or prevent troubles instead of reacting to the troubles when they [...]</description>
		<content:encoded><![CDATA[<p>[...] here 4 &#8211; Anticipating &#8211; we establish routines based on our past experience with them; e.g. explicit risk management activities that help to anticipate or prevent troubles instead of reacting to the troubles when they [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Cultural Patterns of Software Organizations by Scenario Planning is an Illusion &#171; Serendipity</title>
		<link>http://blog.piecemealgrowth.net/cultural-patterns-of-software-organizations/comment-page-1/#comment-12513</link>
		<dc:creator>Scenario Planning is an Illusion &#171; Serendipity</dc:creator>
		<pubDate>Tue, 07 Apr 2009 13:20:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.piecemealgrowth.net/cultural-patterns-of-software-organizations/#comment-12513</guid>
		<description>[...] Planning is an&#160;Illusion  Marc wrote, and I am jumping ahead some here 4 - Anticipating - we establish routines based on our past [...]</description>
		<content:encoded><![CDATA[<p>[...] Planning is an&nbsp;Illusion  Marc wrote, and I am jumping ahead some here 4 &#8211; Anticipating &#8211; we establish routines based on our past [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Agile development and retrospective coherence by Machiel Groeneveld</title>
		<link>http://blog.piecemealgrowth.net/agile-development-and-retrospective-coherence/comment-page-1/#comment-12354</link>
		<dc:creator>Machiel Groeneveld</dc:creator>
		<pubDate>Tue, 17 Mar 2009 06:33:38 +0000</pubDate>
		<guid isPermaLink="false">http://blog.piecemealgrowth.net/?p=153#comment-12354</guid>
		<description>Nice post indeed. I also presented on this &#039;do it by the book&#039; behaviour and Agile conformism. I look at it from a (product) adoption point of view. A set of Agile principles are great for early adopters and innovators, but the large masses desperately need very pragmatic and defined ways of doing things. Scrum + XP fits that need. This also means that, like any non-evolving product, it will die of relatively quickly, much like RUP did (did it die?). Mostly because there will be new ways to &#039;make your entire company competitive (tm)&#039; but also because few people will do Scrum + XP correctly. The large masses also have a tendency to use a watered down version of things (as apposed to &#039;tuned&#039;) and then blame the method for their failure. Perhaps they need some systems thinking to solve that problem ;)</description>
		<content:encoded><![CDATA[<p>Nice post indeed. I also presented on this &#8216;do it by the book&#8217; behaviour and Agile conformism. I look at it from a (product) adoption point of view. A set of Agile principles are great for early adopters and innovators, but the large masses desperately need very pragmatic and defined ways of doing things. Scrum + XP fits that need. This also means that, like any non-evolving product, it will die of relatively quickly, much like RUP did (did it die?). Mostly because there will be new ways to &#8216;make your entire company competitive &#8482;&#8217; but also because few people will do Scrum + XP correctly. The large masses also have a tendency to use a watered down version of things (as apposed to &#8216;tuned&#8217;) and then blame the method for their failure. Perhaps they need some systems thinking to solve that problem <img src='http://blog.piecemealgrowth.net/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Agile development and retrospective coherence by David Harvey</title>
		<link>http://blog.piecemealgrowth.net/agile-development-and-retrospective-coherence/comment-page-1/#comment-12014</link>
		<dc:creator>David Harvey</dc:creator>
		<pubDate>Wed, 11 Feb 2009 09:04:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.piecemealgrowth.net/?p=153#comment-12014</guid>
		<description>Hi Marc,

Good to be reminded of this. Here in the UK we&#039;ve been lucky enough to benefit from David Snowden&#039;s presence. A number of folks in the agile community here and elsewhere - Joseph Pelrine, Steve Freeman, Rachel Davies amongst them - were Cynefin-accredited early on, and have been using these ideas effectively in practice and teaching for a number of years.

It&#039;s important to remember, though, that this is just one model of sensemaking or situational awareness - there are many many others. Sometimes they simply recast things in different ways - you can take your pick, for example, between probe/sense/respond and Scrum&#039;s empirical process control; sometimes they come at things from enough of a different angle to add a new dimension to your understanding (like the work of Ralph Stacey or Karl Weick). 

As technologists we&#039;re regularly beguiled by models (particularly when they use ego-boosting geek words like &quot;chaos&quot; and &quot;complexity&quot; :-) ).

Agreed, too, that retrospective-by-recipe is a surefire way to guarantee that a team won&#039;t get value out of the practice. It&#039;s the most fragile of the agile practices, it depends more than any on a level of maturity and self-awareness in both coaches and teams that I see all to rarely.</description>
		<content:encoded><![CDATA[<p>Hi Marc,</p>
<p>Good to be reminded of this. Here in the UK we&#8217;ve been lucky enough to benefit from David Snowden&#8217;s presence. A number of folks in the agile community here and elsewhere &#8211; Joseph Pelrine, Steve Freeman, Rachel Davies amongst them &#8211; were Cynefin-accredited early on, and have been using these ideas effectively in practice and teaching for a number of years.</p>
<p>It&#8217;s important to remember, though, that this is just one model of sensemaking or situational awareness &#8211; there are many many others. Sometimes they simply recast things in different ways &#8211; you can take your pick, for example, between probe/sense/respond and Scrum&#8217;s empirical process control; sometimes they come at things from enough of a different angle to add a new dimension to your understanding (like the work of Ralph Stacey or Karl Weick). </p>
<p>As technologists we&#8217;re regularly beguiled by models (particularly when they use ego-boosting geek words like &#8220;chaos&#8221; and &#8220;complexity&#8221; <img src='http://blog.piecemealgrowth.net/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' />  ).</p>
<p>Agreed, too, that retrospective-by-recipe is a surefire way to guarantee that a team won&#8217;t get value out of the practice. It&#8217;s the most fragile of the agile practices, it depends more than any on a level of maturity and self-awareness in both coaches and teams that I see all to rarely.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
