<?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: WelfareCSM Day 3: Experimental Mobiles and Rainforest Birds</title>
	<atom:link href="http://www.downtempo.net/blog/agile-and-scrum/welfarecsm-day-3-experimental-mobiles-and-rainforest-birds/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.downtempo.net/blog/agile-and-scrum/welfarecsm-day-3-experimental-mobiles-and-rainforest-birds/</link>
	<description>Product, development, and design musings from your friends at Downtempo</description>
	<lastBuildDate>Tue, 23 Aug 2011 20:46:52 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Catherine</title>
		<link>http://www.downtempo.net/blog/agile-and-scrum/welfarecsm-day-3-experimental-mobiles-and-rainforest-birds/comment-page-1/#comment-810</link>
		<dc:creator>Catherine</dc:creator>
		<pubDate>Tue, 29 Dec 2009 00:25:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.downtempo.net/blog/?p=291#comment-810</guid>
		<description>Tobias&#039; exercise reinforced the importance of the ScrumMaster&#8217;s role in coordinating, communicating, and pulling PO and team efforts together to develop a product that delights the customer.  POs who communicate changing requirements clearly and timely, and work closely with the ScrumMaster(s) are valuable, as ours was.  I also agree with Robi that we learned by doing, not talking.  Actual work, along with the time boxing made for an effective Scrum simulation, since frequent failures quickly helped refine goals and contributed to the product&#039;s acceptance. 
 </description>
		<content:encoded><![CDATA[<p>Tobias&#039; exercise reinforced the importance of the ScrumMaster&rsquo;s role in coordinating, communicating, and pulling PO and team efforts together to develop a product that delights the customer.  POs who communicate changing requirements clearly and timely, and work closely with the ScrumMaster(s) are valuable, as ours was.  I also agree with Robi that we learned by doing, not talking.  Actual work, along with the time boxing made for an effective Scrum simulation, since frequent failures quickly helped refine goals and contributed to the product&#039;s acceptance.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robi</title>
		<link>http://www.downtempo.net/blog/agile-and-scrum/welfarecsm-day-3-experimental-mobiles-and-rainforest-birds/comment-page-1/#comment-743</link>
		<dc:creator>Robi</dc:creator>
		<pubDate>Mon, 28 Dec 2009 03:09:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.downtempo.net/blog/?p=291#comment-743</guid>
		<description>For me, two aspects are memorable take-aways (and, to be honest, I was a bit skeptical as we were getting started).   
 
1.  It highlighted the incredibly important role the product owner holds for the team.  I say this, because in real life, it will not always be possible to have constant interface with the customer (If that was possible, who needs a PO, right?), but the team benefits from the continuous feedback and clarifications.  The PO can/should take on that responsibility, when the customer is not accessible. 
 
2. Making the first prototype(s), and having them reviewed and critiqued by the product owner and customer was INDEED powerful.  And possibly more practical than spending countless cycles planning.  Tobias deliberately pushed us toward &quot;doing&quot; rather than &quot;talking about doing&quot;, and I think it was precisely to experience the rewards of the tangible, real feedback. 
 
Cheers, Robi </description>
		<content:encoded><![CDATA[<p>For me, two aspects are memorable take-aways (and, to be honest, I was a bit skeptical as we were getting started).   </p>
<p>1.  It highlighted the incredibly important role the product owner holds for the team.  I say this, because in real life, it will not always be possible to have constant interface with the customer (If that was possible, who needs a PO, right?), but the team benefits from the continuous feedback and clarifications.  The PO can/should take on that responsibility, when the customer is not accessible. </p>
<p>2. Making the first prototype(s), and having them reviewed and critiqued by the product owner and customer was INDEED powerful.  And possibly more practical than spending countless cycles planning.  Tobias deliberately pushed us toward &quot;doing&quot; rather than &quot;talking about doing&quot;, and I think it was precisely to experience the rewards of the tangible, real feedback. </p>
<p>Cheers, Robi</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: uberVU - social comments</title>
		<link>http://www.downtempo.net/blog/agile-and-scrum/welfarecsm-day-3-experimental-mobiles-and-rainforest-birds/comment-page-1/#comment-453</link>
		<dc:creator>uberVU - social comments</dc:creator>
		<pubDate>Wed, 23 Dec 2009 06:00:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.downtempo.net/blog/?p=291#comment-453</guid>
		<description>&lt;strong&gt;Social comments and analytics for this post...&lt;/strong&gt;

This post was mentioned on Twitter by tobiasgmayer: Write up of Scrum-of-Scrums workshop: &quot;Experimental Mobiles and Rain Forest Birds&quot; http://bit.ly/4vStQL #welfareCSM...</description>
		<content:encoded><![CDATA[<p><strong>Social comments and analytics for this post&#8230;</strong></p>
<p>This post was mentioned on Twitter by tobiasgmayer: Write up of Scrum-of-Scrums workshop: &#8220;Experimental Mobiles and Rain Forest Birds&#8221; <a href="http://bit.ly/4vStQL" rel="nofollow">http://bit.ly/4vStQL</a> #welfareCSM&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tweets that mention DOWNTEMPO -- Topsy.com</title>
		<link>http://www.downtempo.net/blog/agile-and-scrum/welfarecsm-day-3-experimental-mobiles-and-rainforest-birds/comment-page-1/#comment-446</link>
		<dc:creator>Tweets that mention DOWNTEMPO -- Topsy.com</dc:creator>
		<pubDate>Tue, 22 Dec 2009 10:33:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.downtempo.net/blog/?p=291#comment-446</guid>
		<description>[...] This post was mentioned on Twitter by Tobias Mayer, Crackers the Parrot. Crackers the Parrot said: WelfareCSM Day 3: Experimental Mobiles and Rainforest Birds http://bit.ly/6PFOFE [...]</description>
		<content:encoded><![CDATA[<p>[...] This post was mentioned on Twitter by Tobias Mayer, Crackers the Parrot. Crackers the Parrot said: WelfareCSM Day 3: Experimental Mobiles and Rainforest Birds <a href="http://bit.ly/6PFOFE" rel="nofollow">http://bit.ly/6PFOFE</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: downtempo</title>
		<link>http://www.downtempo.net/blog/agile-and-scrum/welfarecsm-day-3-experimental-mobiles-and-rainforest-birds/comment-page-1/#comment-442</link>
		<dc:creator>downtempo</dc:creator>
		<pubDate>Tue, 22 Dec 2009 05:24:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.downtempo.net/blog/?p=291#comment-442</guid>
		<description>Thanks Tobias! One of the thing that impressed me was how quickly the group self-organized productively. Each team focused nicely around their talents, and our PO was a definite rockstar. :)&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Thanks again for another great perspective on the Scrum process. Hope we get a chance to work together again one day!&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;- andy </description>
		<content:encoded><![CDATA[<p>Thanks Tobias! One of the thing that impressed me was how quickly the group self-organized productively. Each team focused nicely around their talents, and our PO was a definite rockstar. <img src='http://www.downtempo.net/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Thanks again for another great perspective on the Scrum process. Hope we get a chance to work together again one day!</p>
<p>- andy</p>
]]></content:encoded>
	</item>
</channel>
</rss>

