<?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: Cause and effect in retrospectives</title>
	<atom:link href="http://www.agiledesign.co.uk/retrospectives/cause-and-effect-in-retrospectives/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.agiledesign.co.uk/retrospectives/cause-and-effect-in-retrospectives/</link>
	<description>Building business agility though software</description>
	<lastBuildDate>Wed, 21 Jul 2010 09:37:52 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Dave</title>
		<link>http://www.agiledesign.co.uk/retrospectives/cause-and-effect-in-retrospectives/comment-page-1/#comment-939</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Wed, 14 Oct 2009 10:55:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.agiledesign.co.uk/retrospectives/cause-and-effect-in-retrospectives/#comment-939</guid>
		<description>Hi David,

I agree that this put&#039;s a focus on the negative and share your concern.

I tend to use this technique within a retrospective structure that provides an opportunity to focus on positives also. As a minimum I will use an &#039;emotional seismograph&#039; to bring into focus both high&#039;s and lows.

As a one off this approach provides a team with a set of intervention points where they have issues to deal with. I would select this tool in particular where individuals have pre-conceptions about root causes of issues and fixes.

I&#039;m not entirely convinced that the neutrality of a diagram of effects would hold for long in practice but look forward to giving it a try. I&#039;m also keen to develop my tool set to include approaches that focus on the positive (maybe AI inspired).

Thanks for the comment.</description>
		<content:encoded><![CDATA[<p>Hi David,</p>
<p>I agree that this put&#8217;s a focus on the negative and share your concern.</p>
<p>I tend to use this technique within a retrospective structure that provides an opportunity to focus on positives also. As a minimum I will use an &#8216;emotional seismograph&#8217; to bring into focus both high&#8217;s and lows.</p>
<p>As a one off this approach provides a team with a set of intervention points where they have issues to deal with. I would select this tool in particular where individuals have pre-conceptions about root causes of issues and fixes.</p>
<p>I&#8217;m not entirely convinced that the neutrality of a diagram of effects would hold for long in practice but look forward to giving it a try. I&#8217;m also keen to develop my tool set to include approaches that focus on the positive (maybe AI inspired).</p>
<p>Thanks for the comment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Harvey</title>
		<link>http://www.agiledesign.co.uk/retrospectives/cause-and-effect-in-retrospectives/comment-page-1/#comment-938</link>
		<dc:creator>David Harvey</dc:creator>
		<pubDate>Tue, 13 Oct 2009 16:44:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.agiledesign.co.uk/retrospectives/cause-and-effect-in-retrospectives/#comment-938</guid>
		<description>I&#039;ve seen a few current reality trees, though not used the technique. Thanks for this succinct explanation. One concern I&#039;d have is about focusing on undesirable/unwanted traits in a scenario: I suspect that this could be counter-productive (accentuating the negative), making it less useful in a team or group where there are conflicts and disagreements about what happened. The diagram of effects is from the start much more neutral. What&#039;s your experience with this?</description>
		<content:encoded><![CDATA[<p>I&#8217;ve seen a few current reality trees, though not used the technique. Thanks for this succinct explanation. One concern I&#8217;d have is about focusing on undesirable/unwanted traits in a scenario: I suspect that this could be counter-productive (accentuating the negative), making it less useful in a team or group where there are conflicts and disagreements about what happened. The diagram of effects is from the start much more neutral. What&#8217;s your experience with this?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dreamfeed &#187; Blog Archive &#187; Systems thinking with diagrams of effects</title>
		<link>http://www.agiledesign.co.uk/retrospectives/cause-and-effect-in-retrospectives/comment-page-1/#comment-936</link>
		<dc:creator>Dreamfeed &#187; Blog Archive &#187; Systems thinking with diagrams of effects</dc:creator>
		<pubDate>Tue, 13 Oct 2009 08:56:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.agiledesign.co.uk/retrospectives/cause-and-effect-in-retrospectives/#comment-936</guid>
		<description>[...] &#8211; diagrams of effects facilitate team problem solving processes (similar to what David Draper is doing with current reality trees, another systems thinking [...]</description>
		<content:encoded><![CDATA[<p>[...] &#8211; diagrams of effects facilitate team problem solving processes (similar to what David Draper is doing with current reality trees, another systems thinking [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
