<?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: What Were They Thinking?</title>
	<atom:link href="http://blog.tastycupcakes.com/2009/06/what-were-they-thinking/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.tastycupcakes.com/2009/06/what-were-they-thinking/</link>
	<description>Fuel for Software Professionals</description>
	<lastBuildDate>Tue, 20 Jul 2010 12:11:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Michael McCullough</title>
		<link>http://blog.tastycupcakes.com/2009/06/what-were-they-thinking/comment-page-1/#comment-45</link>
		<dc:creator>Michael McCullough</dc:creator>
		<pubDate>Mon, 14 Dec 2009 23:12:46 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tastycupcakes.com/?p=22#comment-45</guid>
		<description>Hi Lodewijk! 

Thanks so much for your comment. I agree, many developers understand the imperfection of language to completely describe what is fundamentally an uncertain goal. The intent of this game is to illustrate that point to those less familiar with the nature of building software. 

The idea of changing the game to illustrate the need for feedback in empirical processes sounds really interesting. I wouldn&#039;t say you&#039;re on the wrong track in any way. It is just not the path we went down when we created the game. I would be interested in hearing how this works for you. Perhaps you could even post it as a new game!

Mike</description>
		<content:encoded><![CDATA[<p>Hi Lodewijk! </p>
<p>Thanks so much for your comment. I agree, many developers understand the imperfection of language to completely describe what is fundamentally an uncertain goal. The intent of this game is to illustrate that point to those less familiar with the nature of building software. </p>
<p>The idea of changing the game to illustrate the need for feedback in empirical processes sounds really interesting. I wouldn&#8217;t say you&#8217;re on the wrong track in any way. It is just not the path we went down when we created the game. I would be interested in hearing how this works for you. Perhaps you could even post it as a new game!</p>
<p>Mike</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lodewijk Bergmans</title>
		<link>http://blog.tastycupcakes.com/2009/06/what-were-they-thinking/comment-page-1/#comment-43</link>
		<dc:creator>Lodewijk Bergmans</dc:creator>
		<pubDate>Mon, 14 Dec 2009 22:24:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tastycupcakes.com/?p=22#comment-43</guid>
		<description>I am very much in favor of activating people when learning, and preferably in a fun way.
I do think this is a nice exercise, but I am wondering to what extent we need to let people experience &quot;In software, we are rarely creating something that already exists. So we are forced to communicate in imperatives and metaphors and, quite often, much is lost in translation.&quot;

Certainly almost every developer is aware of this, right?
Now I am wondering if this could be improved (and e.g. &quot;Mr. Happy Face&quot; does a better job at that) to let people experience an alternative way of working: indeed the difference in round 1 and 2 is doing that, but the overall feeling after the game will remain: we have a problem (as we already knew).
So why not have (equally difficult?) assignments where in the last round, additional iteration/feedback cycles are allowed, to show that the result is actually better? (or even continuous feedback while the team is working...)

You could even introduce economics in it, perhaps? -&gt; e.g. cost per time unit, every time you iterate, costs additional, delivering the wrong thing will yield nothing.

If I am on the wrong track with my suggestions; please enlighten me!

cheers,
Lodewijk Bergmans

PS: especially when drawing, this is much like the party game &#039;pictionary&#039;--great fun indeed</description>
		<content:encoded><![CDATA[<p>I am very much in favor of activating people when learning, and preferably in a fun way.<br />
I do think this is a nice exercise, but I am wondering to what extent we need to let people experience &#8220;In software, we are rarely creating something that already exists. So we are forced to communicate in imperatives and metaphors and, quite often, much is lost in translation.&#8221;</p>
<p>Certainly almost every developer is aware of this, right?<br />
Now I am wondering if this could be improved (and e.g. &#8220;Mr. Happy Face&#8221; does a better job at that) to let people experience an alternative way of working: indeed the difference in round 1 and 2 is doing that, but the overall feeling after the game will remain: we have a problem (as we already knew).<br />
So why not have (equally difficult?) assignments where in the last round, additional iteration/feedback cycles are allowed, to show that the result is actually better? (or even continuous feedback while the team is working&#8230;)</p>
<p>You could even introduce economics in it, perhaps? -&gt; e.g. cost per time unit, every time you iterate, costs additional, delivering the wrong thing will yield nothing.</p>
<p>If I am on the wrong track with my suggestions; please enlighten me!</p>
<p>cheers,<br />
Lodewijk Bergmans</p>
<p>PS: especially when drawing, this is much like the party game &#8216;pictionary&#8217;&#8211;great fun indeed</p>
]]></content:encoded>
	</item>
</channel>
</rss>
