<?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 TastyCupcakes.Com</title>
	<atom:link href="http://blog.tastycupcakes.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.tastycupcakes.com</link>
	<description>Fuel for Software Professionals</description>
	<lastBuildDate>Wed, 10 Mar 2010 09:58:42 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Collaborative Origami by Beth Parker</title>
		<link>http://blog.tastycupcakes.com/2009/06/collaborative-origami/comment-page-1/#comment-59</link>
		<dc:creator>Beth Parker</dc:creator>
		<pubDate>Wed, 10 Mar 2010 09:58:42 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tastycupcakes.com/?p=58#comment-59</guid>
		<description>It would be helpful if the article provided the origami instructions! 
Otherwise, good article.</description>
		<content:encoded><![CDATA[<p>It would be helpful if the article provided the origami instructions!<br />
Otherwise, good article.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Resort Brochure by Gwyn Morfey</title>
		<link>http://blog.tastycupcakes.com/2009/06/resort-brochure/comment-page-1/#comment-58</link>
		<dc:creator>Gwyn Morfey</dc:creator>
		<pubDate>Tue, 09 Mar 2010 11:10:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tastycupcakes.com/?p=62#comment-58</guid>
		<description>Thanks for your response. We&#039;re planning to run a big session of this next week, so I&#039;ll let you know how it goes. The idea is to run it as almost the last activity of the day, giving the trainees some practical experience in all the things we&#039;ve been talking about.</description>
		<content:encoded><![CDATA[<p>Thanks for your response. We&#8217;re planning to run a big session of this next week, so I&#8217;ll let you know how it goes. The idea is to run it as almost the last activity of the day, giving the trainees some practical experience in all the things we&#8217;ve been talking about.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Resort Brochure by Don McGreal</title>
		<link>http://blog.tastycupcakes.com/2009/06/resort-brochure/comment-page-1/#comment-57</link>
		<dc:creator>Don McGreal</dc:creator>
		<pubDate>Mon, 08 Mar 2010 23:40:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tastycupcakes.com/?p=62#comment-57</guid>
		<description>Hi Gwyn,
I like having the whole team come up with a wish list of the ultimate resort brochure because it adds originality and fun. However, I then like to ask the teams, based on the creative mess they generated, if they have a clear vision for what the brochure will look like. This is a good time to introduce the role of Product Owner, which each team needs to select. The PO is responsible for prioritizing and reining in the backlog and establishing a vision. During implementation, the PO doesn&#039;t do any of the tasks, but need to be available to the team for questions and feedback. The PO then accepts or rejects the work in the sprint demo. Over time, I have put more and more emphasis on the PO role during this exercise and have found that it enhances it quite a bit.

As a side note, I have stopped asking the teams to write their wish list in the form of user stories. I just ask them to write down what &#039;features&#039; they would like. I have also found that having the PO more involved, I do not have to explicitly ask teams to write acceptance criteria. This simplifies the exercise while staying in step with Scrum, which does not prescribe any user story or acceptance testing templates.
This exercise, however, sets up a great introduction for both techniques later on.

As far as sample stories/features, here are a few common ones:

 * Show off sandy beaches
 * Show people having fun
 * List amenities
 * List activities
 * Adults only. No Kids!
 * Show room sample
 * Display contact information
 * Full bar
 * Golf
 * Resort layout/map
 * Display distance from airport(s)
 * Stands out from other brochures (non-functional)
 * Can be mailed in standard envelope (non-functional)
 * Nude Beaches!

Gwyn, I hope that helps. Please let us know if you have any other questions.
We would love to hear your experiences if you choose to use this one (or any others).

Thanks,

Don</description>
		<content:encoded><![CDATA[<p>Hi Gwyn,<br />
I like having the whole team come up with a wish list of the ultimate resort brochure because it adds originality and fun. However, I then like to ask the teams, based on the creative mess they generated, if they have a clear vision for what the brochure will look like. This is a good time to introduce the role of Product Owner, which each team needs to select. The PO is responsible for prioritizing and reining in the backlog and establishing a vision. During implementation, the PO doesn&#8217;t do any of the tasks, but need to be available to the team for questions and feedback. The PO then accepts or rejects the work in the sprint demo. Over time, I have put more and more emphasis on the PO role during this exercise and have found that it enhances it quite a bit.</p>
<p>As a side note, I have stopped asking the teams to write their wish list in the form of user stories. I just ask them to write down what &#8216;features&#8217; they would like. I have also found that having the PO more involved, I do not have to explicitly ask teams to write acceptance criteria. This simplifies the exercise while staying in step with Scrum, which does not prescribe any user story or acceptance testing templates.<br />
This exercise, however, sets up a great introduction for both techniques later on.</p>
<p>As far as sample stories/features, here are a few common ones:</p>
<p> * Show off sandy beaches<br />
 * Show people having fun<br />
 * List amenities<br />
 * List activities<br />
 * Adults only. No Kids!<br />
 * Show room sample<br />
 * Display contact information<br />
 * Full bar<br />
 * Golf<br />
 * Resort layout/map<br />
 * Display distance from airport(s)<br />
 * Stands out from other brochures (non-functional)<br />
 * Can be mailed in standard envelope (non-functional)<br />
 * Nude Beaches!</p>
<p>Gwyn, I hope that helps. Please let us know if you have any other questions.<br />
We would love to hear your experiences if you choose to use this one (or any others).</p>
<p>Thanks,</p>
<p>Don</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Resort Brochure by Gwyn Morfey</title>
		<link>http://blog.tastycupcakes.com/2009/06/resort-brochure/comment-page-1/#comment-56</link>
		<dc:creator>Gwyn Morfey</dc:creator>
		<pubDate>Mon, 08 Mar 2010 16:28:33 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tastycupcakes.com/?p=62#comment-56</guid>
		<description>Looks to me like the players start off as customers (or customer proxies) for the user stories workshop, then switch to developers and stay that way. Is that right? Would it be useful to remove the ambiguity by pre-generating the stories, or by having crew act as customer proxies?

If this is a good option, do you have a stack of sample stories for this game?</description>
		<content:encoded><![CDATA[<p>Looks to me like the players start off as customers (or customer proxies) for the user stories workshop, then switch to developers and stay that way. Is that right? Would it be useful to remove the ambiguity by pre-generating the stories, or by having crew act as customer proxies?</p>
<p>If this is a good option, do you have a stack of sample stories for this game?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on 99 Test Balloons by Mick Maguire</title>
		<link>http://blog.tastycupcakes.com/2009/06/99-test-balloons/comment-page-1/#comment-54</link>
		<dc:creator>Mick Maguire</dc:creator>
		<pubDate>Thu, 11 Feb 2010 17:53:59 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tastycupcakes.com/?p=69#comment-54</guid>
		<description>Tried this with my teams - a lot of fun, but there were questions of acceptance right up front. So, it&#039;s good to have a strategy in mind to deal with that beforehand.</description>
		<content:encoded><![CDATA[<p>Tried this with my teams &#8211; a lot of fun, but there were questions of acceptance right up front. So, it&#8217;s good to have a strategy in mind to deal with that beforehand.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Thumb Wars by Doc</title>
		<link>http://blog.tastycupcakes.com/2010/01/thumb-wars/comment-page-1/#comment-53</link>
		<dc:creator>Doc</dc:creator>
		<pubDate>Mon, 01 Feb 2010 18:56:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tastycupcakes.com/?p=417#comment-53</guid>
		<description>I like this one - now to find an opportunity to use it.  Hmm...</description>
		<content:encoded><![CDATA[<p>I like this one &#8211; now to find an opportunity to use it.  Hmm&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Process Doodle by The Endowment Effect (Cognitive Bias) &#124; The Doctor Is In</title>
		<link>http://blog.tastycupcakes.com/2009/06/process-doodle/comment-page-1/#comment-52</link>
		<dc:creator>The Endowment Effect (Cognitive Bias) &#124; The Doctor Is In</dc:creator>
		<pubDate>Fri, 29 Jan 2010 22:50:49 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tastycupcakes.com/?p=86#comment-52</guid>
		<description>[...] one client I worked with recently, we had the group split into two teams, and had each team do a process doodle. As part of the exercise, each group explains their doodle. Both teams that participated explained [...]</description>
		<content:encoded><![CDATA[<p>[...] one client I worked with recently, we had the group split into two teams, and had each team do a process doodle. As part of the exercise, each group explains their doodle. Both teams that participated explained [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Doggy Planning by Don McGreal</title>
		<link>http://blog.tastycupcakes.com/2009/06/doggy-planning/comment-page-1/#comment-50</link>
		<dc:creator>Don McGreal</dc:creator>
		<pubDate>Fri, 15 Jan 2010 05:01:45 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tastycupcakes.com/?p=50#comment-50</guid>
		<description>Hi Russell,

Thanks for your comment!
No, I do not ever show pictures of the dogs. Although, I just realized that the write-up does not make that clear. I will update it.
It works better when voters are just giving their best guess at the relative size based on their current knowledge. This makes it easier to correlate to software features. I also like it when I get people voting on the poodle based on their initial assumptions (toy vs. standard). The votes expose the assumptions, so we clarify and re-vote. Having pictures of the poodle would make it harder to expose this.
With lesser known dogs, like the Newfoundland, some voters will actually google the dog in order to show others what it looks like before the re-vote. Again, a picture would prevent this.

I totally agree that relative sizing should be a learning point. I don&#039;t know why I missed it. I&#039;ll update that too!

Thanks for the great feedback Russell!

Don</description>
		<content:encoded><![CDATA[<p>Hi Russell,</p>
<p>Thanks for your comment!<br />
No, I do not ever show pictures of the dogs. Although, I just realized that the write-up does not make that clear. I will update it.<br />
It works better when voters are just giving their best guess at the relative size based on their current knowledge. This makes it easier to correlate to software features. I also like it when I get people voting on the poodle based on their initial assumptions (toy vs. standard). The votes expose the assumptions, so we clarify and re-vote. Having pictures of the poodle would make it harder to expose this.<br />
With lesser known dogs, like the Newfoundland, some voters will actually google the dog in order to show others what it looks like before the re-vote. Again, a picture would prevent this.</p>
<p>I totally agree that relative sizing should be a learning point. I don&#8217;t know why I missed it. I&#8217;ll update that too!</p>
<p>Thanks for the great feedback Russell!</p>
<p>Don</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on People Polling by Mick Maguire</title>
		<link>http://blog.tastycupcakes.com/2009/07/people-polling/comment-page-1/#comment-49</link>
		<dc:creator>Mick Maguire</dc:creator>
		<pubDate>Tue, 12 Jan 2010 19:22:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tastycupcakes.com/?p=264#comment-49</guid>
		<description>First attempt for me didn&#039;t work so well. I put 375 dots on a small whiteboard then showed it to my audience. Estimates ranged from 150 - 400 dots with an average of 252. The average fell only just within the top 50th percentile of averages from the group and was not clearly more reliable than asking an individual. As you say &quot;there is always a chance that the results could be off&quot;, and it did lead to a good discussion about the exercise itself.</description>
		<content:encoded><![CDATA[<p>First attempt for me didn&#8217;t work so well. I put 375 dots on a small whiteboard then showed it to my audience. Estimates ranged from 150 &#8211; 400 dots with an average of 252. The average fell only just within the top 50th percentile of averages from the group and was not clearly more reliable than asking an individual. As you say &#8220;there is always a chance that the results could be off&#8221;, and it did lead to a good discussion about the exercise itself.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Doggy Planning by Russell Norlund</title>
		<link>http://blog.tastycupcakes.com/2009/06/doggy-planning/comment-page-1/#comment-48</link>
		<dc:creator>Russell Norlund</dc:creator>
		<pubDate>Tue, 05 Jan 2010 09:56:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tastycupcakes.com/?p=50#comment-48</guid>
		<description>Hi Folks, I have a few questions about the doggy planning game:

- Do you need to show actual pictures of the dogs or do you just need story cards with the dogs names?
- I guess another learning point is that the game emphasises the relative size aspect of story points

Thanks for making this resource available.

Kind Regards

Russell</description>
		<content:encoded><![CDATA[<p>Hi Folks, I have a few questions about the doggy planning game:</p>
<p>- Do you need to show actual pictures of the dogs or do you just need story cards with the dogs names?<br />
- I guess another learning point is that the game emphasises the relative size aspect of story points</p>
<p>Thanks for making this resource available.</p>
<p>Kind Regards</p>
<p>Russell</p>
]]></content:encoded>
	</item>
</channel>
</rss>
