<?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: Examples make it easy to spot inconsistencies</title>
	<atom:link href="http://gojko.net/2009/05/12/examples-make-it-easy-to-spot-inconsistencies/feed/" rel="self" type="application/rss+xml" />
	<link>http://gojko.net/2009/05/12/examples-make-it-easy-to-spot-inconsistencies/</link>
	<description>Building software that matters</description>
	<lastBuildDate>Fri, 18 May 2012 13:40:15 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Progressive .NET Exchange @ YABoW @ trappers.tk</title>
		<link>http://gojko.net/2009/05/12/examples-make-it-easy-to-spot-inconsistencies/comment-page-1/#comment-48583</link>
		<dc:creator>Progressive .NET Exchange @ YABoW @ trappers.tk</dc:creator>
		<pubDate>Fri, 22 May 2009 12:38:59 +0000</pubDate>
		<guid isPermaLink="false">http://gojko.net/?p=896#comment-48583</guid>
		<description>[...] conference had 2 concurrent tracks to choose from. On the first day I chose to go to Gojko Adzics sessions on specification by example and fitnesse. In this session Gojko presented the idea to use examples [...]</description>
		<content:encoded><![CDATA[<p>[...] conference had 2 concurrent tracks to choose from. On the first day I chose to go to Gojko Adzics sessions on specification by example and fitnesse. In this session Gojko presented the idea to use examples [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robin Minto</title>
		<link>http://gojko.net/2009/05/12/examples-make-it-easy-to-spot-inconsistencies/comment-page-1/#comment-47991</link>
		<dc:creator>Robin Minto</dc:creator>
		<pubDate>Sat, 16 May 2009 09:39:10 +0000</pubDate>
		<guid isPermaLink="false">http://gojko.net/?p=896#comment-47991</guid>
		<description>I enjoyed the workshop (good write-up too) - I think it worked remarkably well given that we formed teams that had never worked together to look at a relatively unknown domain, which highlights the benefits of the techniques.

I&#039;ll be interested to see what comes out from this the next time I&#039;m dealing with specification in my own problem domain.

It was also very valuable to be able to put examples from the morning session to use within Fitnesse in the afternoon. I had never actually used Fitnesse (perhaps illustrated by my description to Dylan!) and I found it useful to start using it with a non-trivial domain that was new but where I had some understanding from the morning&#039;s examples. Also, it wasn&#039;t my problem domain where I might be distracted. I could concentrate on the tool rather than the domain.

Thanks for both sessions, Gojko.</description>
		<content:encoded><![CDATA[<p>I enjoyed the workshop (good write-up too) &#8211; I think it worked remarkably well given that we formed teams that had never worked together to look at a relatively unknown domain, which highlights the benefits of the techniques.</p>
<p>I&#8217;ll be interested to see what comes out from this the next time I&#8217;m dealing with specification in my own problem domain.</p>
<p>It was also very valuable to be able to put examples from the morning session to use within Fitnesse in the afternoon. I had never actually used Fitnesse (perhaps illustrated by my description to Dylan!) and I found it useful to start using it with a non-trivial domain that was new but where I had some understanding from the morning&#8217;s examples. Also, it wasn&#8217;t my problem domain where I might be distracted. I could concentrate on the tool rather than the domain.</p>
<p>Thanks for both sessions, Gojko.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Markus Gärtner</title>
		<link>http://gojko.net/2009/05/12/examples-make-it-easy-to-spot-inconsistencies/comment-page-1/#comment-47702</link>
		<dc:creator>Markus Gärtner</dc:creator>
		<pubDate>Wed, 13 May 2009 19:24:38 +0000</pubDate>
		<guid isPermaLink="false">http://gojko.net/?p=896#comment-47702</guid>
		<description>I&#039;m still looking for a good example in my company. I had found one in our design documents, where similar issues were describes in tables already, but this particular condition was noted in textual form. The prose let out one particular type and I translated it into a table which directly grasped the idea of the requirements there. Unfortunately it was not a breakthrough for management buy-in, but I&#039;ll be working on this in the next few months.

On the star picture: For a presentation at my company I was considering bringing up the five pointed star, write down the answers and before collecting the answers show up the 12 and 24 pointed stars from the book, ask to write down which star has 12 points and if each one was considering to adjust the number of points in the previous image. Too much for a presenation, but for an introduction workshop into Specification by Example useful since it gets the attention of the participants.</description>
		<content:encoded><![CDATA[<p>I&#8217;m still looking for a good example in my company. I had found one in our design documents, where similar issues were describes in tables already, but this particular condition was noted in textual form. The prose let out one particular type and I translated it into a table which directly grasped the idea of the requirements there. Unfortunately it was not a breakthrough for management buy-in, but I&#8217;ll be working on this in the next few months.</p>
<p>On the star picture: For a presentation at my company I was considering bringing up the five pointed star, write down the answers and before collecting the answers show up the 12 and 24 pointed stars from the book, ask to write down which star has 12 points and if each one was considering to adjust the number of points in the previous image. Too much for a presenation, but for an introduction workshop into Specification by Example useful since it gets the attention of the participants.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lisa Crispin</title>
		<link>http://gojko.net/2009/05/12/examples-make-it-easy-to-spot-inconsistencies/comment-page-1/#comment-47580</link>
		<dc:creator>Lisa Crispin</dc:creator>
		<pubDate>Tue, 12 May 2009 15:23:28 +0000</pubDate>
		<guid isPermaLink="false">http://gojko.net/?p=896#comment-47580</guid>
		<description>What great exercises! It sounds like the participants got a real-life experience of how examples can help, and how easy it can be to miss inconsistencies.</description>
		<content:encoded><![CDATA[<p>What great exercises! It sounds like the participants got a real-life experience of how examples can help, and how easy it can be to miss inconsistencies.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dylan</title>
		<link>http://gojko.net/2009/05/12/examples-make-it-easy-to-spot-inconsistencies/comment-page-1/#comment-47573</link>
		<dc:creator>Dylan</dc:creator>
		<pubDate>Tue, 12 May 2009 13:34:13 +0000</pubDate>
		<guid isPermaLink="false">http://gojko.net/?p=896#comment-47573</guid>
		<description>I thought the workshops were really interesting - especially the way that around 10:30 we were sat around getting *very* confused about the rules of blackjack and by 13:00 had actually eliminated a lot of the ambiguity, come up with a system for naming and classifying examples, and generally made some real progress in developing a shared understanding of the problem domain. I thought this was a really good example of how &#039;real&#039; projects happen - and having the process distilled into four hours worked really well.

One idea. Next time you do the thing with the star, don&#039;t put the picture up first and ask people to write down how many points it has. Why not ask everyone in the room to &quot;draw a star with ten points&quot; - and see how many different shapes you get? It&#039;d make the same point about ambiguity but avoid the &quot;trick answers&quot; like including the four corners of the display, etc... Just an idea :)

Yesterday morning I didn&#039;t know what acceptance testing was and I&#039;d never heard of Fitnesse (although I liked Robin Minto&#039;s description of Fitnesse as &quot;a wiki with red and green bits&quot;) Now I have a much better idea of what it is, why it&#039;s useful, and when it might be usefully applied. Good stuff all round.</description>
		<content:encoded><![CDATA[<p>I thought the workshops were really interesting &#8211; especially the way that around 10:30 we were sat around getting *very* confused about the rules of blackjack and by 13:00 had actually eliminated a lot of the ambiguity, come up with a system for naming and classifying examples, and generally made some real progress in developing a shared understanding of the problem domain. I thought this was a really good example of how &#8216;real&#8217; projects happen &#8211; and having the process distilled into four hours worked really well.</p>
<p>One idea. Next time you do the thing with the star, don&#8217;t put the picture up first and ask people to write down how many points it has. Why not ask everyone in the room to &#8220;draw a star with ten points&#8221; &#8211; and see how many different shapes you get? It&#8217;d make the same point about ambiguity but avoid the &#8220;trick answers&#8221; like including the four corners of the display, etc&#8230; Just an idea <img src='http://gojko.net/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Yesterday morning I didn&#8217;t know what acceptance testing was and I&#8217;d never heard of Fitnesse (although I liked Robin Minto&#8217;s description of Fitnesse as &#8220;a wiki with red and green bits&#8221;) Now I have a much better idea of what it is, why it&#8217;s useful, and when it might be usefully applied. Good stuff all round.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

