<?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 We Do Things &#8211; Specification (Using the right tools)</title>
	<atom:link href="http://lostechies.com/scottreynolds/2009/11/13/how-we-do-things-specification-using-the-right-tools/feed/" rel="self" type="application/rss+xml" />
	<link>http://lostechies.com/scottreynolds/2009/11/13/how-we-do-things-specification-using-the-right-tools/</link>
	<description>Just another LosTechies site</description>
	<lastBuildDate>Fri, 25 Mar 2011 10:26:03 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.2</generator>
	<item>
		<title>By: Michael Iantosca</title>
		<link>http://lostechies.com/scottreynolds/2009/11/13/how-we-do-things-specification-using-the-right-tools/#comment-179</link>
		<dc:creator>Michael Iantosca</dc:creator>
		<pubDate>Tue, 24 Nov 2009 12:00:54 +0000</pubDate>
		<guid isPermaLink="false">/blogs/scottcreynolds/archive/2009/11/13/how-we-do-things-specification-using-the-right-tools.aspx#comment-179</guid>
		<description>great post Scott 

I use mockups/sketches extensively - visio, paper &amp; pen and more recently sketchflow. Iteration with the customer in this process has been key to delivering a great end product. I recently inherited a project that was done by a large(ish) consulting firm that did very little iteration and the end product was not what anyone expected.

I never thought of a high fidelity design as a &quot;limiter&quot; when handed to a developer  - but you are so right. I have fallen into the trap myself as a developer.  I have also been frustrated when developers working with me come back with their end product and don&#039;t think beyond the shiny design.

I look forward to reading the rest of the series
Michael
</description>
		<content:encoded><![CDATA[<p>great post Scott </p>
<p>I use mockups/sketches extensively &#8211; visio, paper &#038; pen and more recently sketchflow. Iteration with the customer in this process has been key to delivering a great end product. I recently inherited a project that was done by a large(ish) consulting firm that did very little iteration and the end product was not what anyone expected.</p>
<p>I never thought of a high fidelity design as a &#8220;limiter&#8221; when handed to a developer  &#8211; but you are so right. I have fallen into the trap myself as a developer.  I have also been frustrated when developers working with me come back with their end product and don&#8217;t think beyond the shiny design.</p>
<p>I look forward to reading the rest of the series<br />
Michael</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott C Reynolds</title>
		<link>http://lostechies.com/scottreynolds/2009/11/13/how-we-do-things-specification-using-the-right-tools/#comment-178</link>
		<dc:creator>Scott C Reynolds</dc:creator>
		<pubDate>Fri, 13 Nov 2009 17:21:14 +0000</pubDate>
		<guid isPermaLink="false">/blogs/scottcreynolds/archive/2009/11/13/how-we-do-things-specification-using-the-right-tools.aspx#comment-178</guid>
		<description>It really depends on the context of the whiteboard session. If it&#039;s done right when we&#039;re going to start on something (or in the middle of something and discussing further) then there may be no &quot;deliverable&quot; at all, because it&#039;s fresh.

Sometimes it may be a picture attached to a story card, sometimes just a few added acceptance criteria, sometimes a mockup. Basically, whatever feels right.</description>
		<content:encoded><![CDATA[<p>It really depends on the context of the whiteboard session. If it&#8217;s done right when we&#8217;re going to start on something (or in the middle of something and discussing further) then there may be no &#8220;deliverable&#8221; at all, because it&#8217;s fresh.</p>
<p>Sometimes it may be a picture attached to a story card, sometimes just a few added acceptance criteria, sometimes a mockup. Basically, whatever feels right.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Corey Coogan</title>
		<link>http://lostechies.com/scottreynolds/2009/11/13/how-we-do-things-specification-using-the-right-tools/#comment-177</link>
		<dc:creator>Corey Coogan</dc:creator>
		<pubDate>Fri, 13 Nov 2009 16:56:28 +0000</pubDate>
		<guid isPermaLink="false">/blogs/scottcreynolds/archive/2009/11/13/how-we-do-things-specification-using-the-right-tools.aspx#comment-177</guid>
		<description>Hi Scott,
     I&#039;m really enjoying your series.  Much of what you are saying rings true for me and I&#039;ve been struggling trying to get clients away from BDUF for a while.  I will be using some of your arguments to augment my own in my quest to eliminate BDUF.

http://blog.coreycoogan.com/2009/06/05/big-design-up-front-bduf-booooo/

I also share your views for using both textual stories and Balsamiq, which totally rocks (http://blog.coreycoogan.com/2009/07/24/mockup-alternative-to-visio-and-powerpoint/).  I&#039;m a big fan of the whiteboard as well and hammering out specs.  

What is typically your deliverable from a whiteboard session?  Is it a mockup and story?  Or does it result in some other artifact that includes a picture of the whiteboard?

</description>
		<content:encoded><![CDATA[<p>Hi Scott,<br />
     I&#8217;m really enjoying your series.  Much of what you are saying rings true for me and I&#8217;ve been struggling trying to get clients away from BDUF for a while.  I will be using some of your arguments to augment my own in my quest to eliminate BDUF.</p>
<p><a href="http://blog.coreycoogan.com/2009/06/05/big-design-up-front-bduf-booooo/" rel="nofollow">http://blog.coreycoogan.com/2009/06/05/big-design-up-front-bduf-booooo/</a></p>
<p>I also share your views for using both textual stories and Balsamiq, which totally rocks (<a href="http://blog.coreycoogan.com/2009/07/24/mockup-alternative-to-visio-and-powerpoint/" rel="nofollow">http://blog.coreycoogan.com/2009/07/24/mockup-alternative-to-visio-and-powerpoint/</a>).  I&#8217;m a big fan of the whiteboard as well and hammering out specs.  </p>
<p>What is typically your deliverable from a whiteboard session?  Is it a mockup and story?  Or does it result in some other artifact that includes a picture of the whiteboard?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
