<?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: How do you keep the chickens from clucking?</title>
	<atom:link href="http://edgehopper.com/how-do-you-keep-the-chickens-from-clucking/feed/" rel="self" type="application/rss+xml" />
	<link>http://edgehopper.com/how-do-you-keep-the-chickens-from-clucking/</link>
	<description>Brain Droppings on Innovation, Creativity, and Collaboration</description>
	<lastBuildDate>Thu, 10 May 2012 09:19:33 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: C B</title>
		<link>http://edgehopper.com/how-do-you-keep-the-chickens-from-clucking/comment-page-1/#comment-7882</link>
		<dc:creator>C B</dc:creator>
		<pubDate>Wed, 24 Aug 2011 00:03:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.chrisspagnuolo.com/PermaLink,guid,02df9b19-c458-4d12-bd31-6dd49ab5d1c1.aspx#comment-7882</guid>
		<description>...and sorry for the double post - had some problems with that captcha!</description>
		<content:encoded><![CDATA[<p>&#8230;and sorry for the double post &#8211; had some problems with that captcha!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: C B</title>
		<link>http://edgehopper.com/how-do-you-keep-the-chickens-from-clucking/comment-page-1/#comment-7881</link>
		<dc:creator>C B</dc:creator>
		<pubDate>Wed, 24 Aug 2011 00:02:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.chrisspagnuolo.com/PermaLink,guid,02df9b19-c458-4d12-bd31-6dd49ab5d1c1.aspx#comment-7881</guid>
		<description>Interesting to hear other perspectives on this topic.  I could not help but think, this seems to be broader than Scrum, it is a general meeting effectiveness issue.  Most meetings that are held in corporate environments could use the lessons of a) inviting only people with stakes in the topic, b) having a clear agenda, c) designating a moderator/facilitator for the meeting...etc.  These are part of &quot;standard practice&quot; for effective meetings.

I was once faced with the challenge of dealing with folks that really liked to interrupt each other (sometimes by yelling) in conversation within a meeting context.  Eventually, the approach that ended up working was to bring a rubber duck (yeah, a yellow rubber duck, beak and everything) into the meeting.  I set an initial goal with the group that we all need to take the time to listen to each other better - so, only the person holding the duck was allowed to speak.  Sort of like a little toy semaphore.  I was worried that it would come off as belittling, but it turned out to inject some humor into the meeting atmosphere.  So the problem became how to improve the teams throw and catch skills - but the conflict got reduced a bit.

Anyway - thanks for the post mate.</description>
		<content:encoded><![CDATA[<p>Interesting to hear other perspectives on this topic.  I could not help but think, this seems to be broader than Scrum, it is a general meeting effectiveness issue.  Most meetings that are held in corporate environments could use the lessons of a) inviting only people with stakes in the topic, b) having a clear agenda, c) designating a moderator/facilitator for the meeting&#8230;etc.  These are part of &#8220;standard practice&#8221; for effective meetings.</p>
<p>I was once faced with the challenge of dealing with folks that really liked to interrupt each other (sometimes by yelling) in conversation within a meeting context.  Eventually, the approach that ended up working was to bring a rubber duck (yeah, a yellow rubber duck, beak and everything) into the meeting.  I set an initial goal with the group that we all need to take the time to listen to each other better &#8211; so, only the person holding the duck was allowed to speak.  Sort of like a little toy semaphore.  I was worried that it would come off as belittling, but it turned out to inject some humor into the meeting atmosphere.  So the problem became how to improve the teams throw and catch skills &#8211; but the conflict got reduced a bit.</p>
<p>Anyway &#8211; thanks for the post mate.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: C B</title>
		<link>http://edgehopper.com/how-do-you-keep-the-chickens-from-clucking/comment-page-1/#comment-7878</link>
		<dc:creator>C B</dc:creator>
		<pubDate>Wed, 24 Aug 2011 00:00:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.chrisspagnuolo.com/PermaLink,guid,02df9b19-c458-4d12-bd31-6dd49ab5d1c1.aspx#comment-7878</guid>
		<description>Interesting to hear other perspectives on this topic.  I could not help but think, this seems to be broader than Scrum, it is a general meeting effectiveness issue.  Most meetings that are held in corporate environments could use the lessons of a) inviting only people with stakes in the topic, b) having a clear agenda, c) designating a moderator/facilitator for the meeting...etc.  These are part of &quot;standard practice&quot; for effective meetings.

I was once faced with the challenge of dealing with folks that really liked to interrupt each other (sometimes by yelling) in conversation within a meeting context.  Eventually, the approach that ended up working was to bring a rubber duck (yeah, a yellow rubber duck, beak and everything) into the meeting.  I set an initial goal with the group that we all need to take the time to listen to each other better - so, only the person holding the duck was allowed to speak.  Sort of like a little toy semaphore.  I was worried that it would come off as belittling, but it turned out to inject some humor into the meeting atmosphere.  So the problem became how to improve the teams throw and catch skills - but the conflict got reduced a bit.

Anyways - thanks for the post an</description>
		<content:encoded><![CDATA[<p>Interesting to hear other perspectives on this topic.  I could not help but think, this seems to be broader than Scrum, it is a general meeting effectiveness issue.  Most meetings that are held in corporate environments could use the lessons of a) inviting only people with stakes in the topic, b) having a clear agenda, c) designating a moderator/facilitator for the meeting&#8230;etc.  These are part of &#8220;standard practice&#8221; for effective meetings.</p>
<p>I was once faced with the challenge of dealing with folks that really liked to interrupt each other (sometimes by yelling) in conversation within a meeting context.  Eventually, the approach that ended up working was to bring a rubber duck (yeah, a yellow rubber duck, beak and everything) into the meeting.  I set an initial goal with the group that we all need to take the time to listen to each other better &#8211; so, only the person holding the duck was allowed to speak.  Sort of like a little toy semaphore.  I was worried that it would come off as belittling, but it turned out to inject some humor into the meeting atmosphere.  So the problem became how to improve the teams throw and catch skills &#8211; but the conflict got reduced a bit.</p>
<p>Anyways &#8211; thanks for the post an</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Served from: edgehopper.com @ 2012-05-21 12:29:43 -->
