<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.1" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Why Write A Functional Specification?</title>
	<link>http://www.mediacrumb.com/2007/05/17/why-write-a-functional-specification/</link>
	<description>We Build Kickass Websites and Applications so you don't have too.</description>
	<pubDate>Tue, 06 Jan 2009 01:50:44 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.1</generator>

	<item>
		<title>By: Justin</title>
		<link>http://www.mediacrumb.com/2007/05/17/why-write-a-functional-specification/#comment-790</link>
		<author>Justin</author>
		<pubDate>Mon, 28 May 2007 18:06:43 +0000</pubDate>
		<guid>http://www.mediacrumb.com/2007/05/17/why-write-a-functional-specification/#comment-790</guid>
					<description>Hey nice post! I'd like to suggest another great tool for visualizing a design through your users eyes. This idea is inline with what you were saying about how just writing the spec can help generate new ideas 

"As you write you’ll have a few Epiphanies..." 

Write use case scenario's!  It's really pretty simple and kinda fun. What you do is take a persona that you've created, take a primary use case and write a few paragraphs of what tasks your persona needs to complete in order to fulfill their goal on your site. 

Literally walk through the process you're thinking about designing/developing on your site. This is a lot like writing a story, you should have fun with it, be specific, but have fun. I think you'll be surprised how much this "talking out loud" helps you visualize your design.

This should really be done with all of your primary use cases. Anyway, there ya go.</description>
		<content:encoded><![CDATA[<p>Hey nice post! I&#8217;d like to suggest another great tool for visualizing a design through your users eyes. This idea is inline with what you were saying about how just writing the spec can help generate new ideas </p>
<p>&#8220;As you write you’ll have a few Epiphanies&#8230;&#8221; </p>
<p>Write use case scenario&#8217;s!  It&#8217;s really pretty simple and kinda fun. What you do is take a persona that you&#8217;ve created, take a primary use case and write a few paragraphs of what tasks your persona needs to complete in order to fulfill their goal on your site. </p>
<p>Literally walk through the process you&#8217;re thinking about designing/developing on your site. This is a lot like writing a story, you should have fun with it, be specific, but have fun. I think you&#8217;ll be surprised how much this &#8220;talking out loud&#8221; helps you visualize your design.</p>
<p>This should really be done with all of your primary use cases. Anyway, there ya go.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: analysis_manager</title>
		<link>http://www.mediacrumb.com/2007/05/17/why-write-a-functional-specification/#comment-2115</link>
		<author>analysis_manager</author>
		<pubDate>Thu, 06 Sep 2007 07:36:07 +0000</pubDate>
		<guid>http://www.mediacrumb.com/2007/05/17/why-write-a-functional-specification/#comment-2115</guid>
					<description>Hi Derrick,

I could not agree with you more!  The agile movement keeps on insisting that the code is the documentation and that functional specs are a waste of time.  The reality is very different... Large projects fail from lack of upfront design and current documentation.

- Adrian</description>
		<content:encoded><![CDATA[<p>Hi Derrick,</p>
<p>I could not agree with you more!  The agile movement keeps on insisting that the code is the documentation and that functional specs are a waste of time.  The reality is very different&#8230; Large projects fail from lack of upfront design and current documentation.</p>
<p>- Adrian</p>
]]></content:encoded>
				</item>
</channel>
</rss>
