<?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: Don&#8217;t write vague use cases, write concrete, specific use cases</title>
	<atom:link href="http://healyourchurchwebsite.com/2007/07/20/dont-write-vague-use-cases-write-concrete-specific-use-cases/feed/" rel="self" type="application/rss+xml" />
	<link>http://healyourchurchwebsite.com/2007/07/20/dont-write-vague-use-cases-write-concrete-specific-use-cases/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=dont-write-vague-use-cases-write-concrete-specific-use-cases</link>
	<description>Teaching, rebuking, correcting &#38; training in righteous web design.</description>
	<lastBuildDate>Mon, 26 Sep 2011 02:56:07 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: 5 things we can learn from the Winston-Salem Hampton-Inn Toaster Czar &#187; Heal Your Church WebSite</title>
		<link>http://healyourchurchwebsite.com/2007/07/20/dont-write-vague-use-cases-write-concrete-specific-use-cases/comment-page-1/#comment-4049</link>
		<dc:creator>5 things we can learn from the Winston-Salem Hampton-Inn Toaster Czar &#187; Heal Your Church WebSite</dc:creator>
		<pubDate>Tue, 03 Jun 2008 17:28:29 +0000</pubDate>
		<guid isPermaLink="false">http://healyourchurchwebsite.com/2007/07/20/dont-write-vague-use-cases-write-concrete-specific-use-cases/#comment-4049</guid>
		<description>[...] - so don&#8217;t assume you completely understand their interface to your system without collecting realistic and specific usage metrics and spending some time setting next to them while they demonstrate how they navigate your site the [...]</description>
		<content:encoded><![CDATA[<p>[...] &#8211; so don&#8217;t assume you completely understand their interface to your system without collecting realistic and specific usage metrics and spending some time setting next to them while they demonstrate how they navigate your site the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 10 things we can learn from the Royal Institute for Interfaith Studies website &#187; Heal Your Church WebSite</title>
		<link>http://healyourchurchwebsite.com/2007/07/20/dont-write-vague-use-cases-write-concrete-specific-use-cases/comment-page-1/#comment-3809</link>
		<dc:creator>10 things we can learn from the Royal Institute for Interfaith Studies website &#187; Heal Your Church WebSite</dc:creator>
		<pubDate>Wed, 14 Nov 2007 20:40:29 +0000</pubDate>
		<guid isPermaLink="false">http://healyourchurchwebsite.com/2007/07/20/dont-write-vague-use-cases-write-concrete-specific-use-cases/#comment-3809</guid>
		<description>[...] in user testing - where non-geeks attempt simple, common [...]</description>
		<content:encoded><![CDATA[<p>[...] in user testing &#8211; where non-geeks attempt simple, common [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: &#187; Heal Your Church WebSite</title>
		<link>http://healyourchurchwebsite.com/2007/07/20/dont-write-vague-use-cases-write-concrete-specific-use-cases/comment-page-1/#comment-3806</link>
		<dc:creator>&#187; Heal Your Church WebSite</dc:creator>
		<pubDate>Tue, 13 Nov 2007 17:30:57 +0000</pubDate>
		<guid isPermaLink="false">http://healyourchurchwebsite.com/2007/07/20/dont-write-vague-use-cases-write-concrete-specific-use-cases/#comment-3806</guid>
		<description>[...] in user testing - where non-geeks attempt simple, common [...]</description>
		<content:encoded><![CDATA[<p>[...] in user testing &#8211; where non-geeks attempt simple, common [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MeanDean</title>
		<link>http://healyourchurchwebsite.com/2007/07/20/dont-write-vague-use-cases-write-concrete-specific-use-cases/comment-page-1/#comment-3622</link>
		<dc:creator>MeanDean</dc:creator>
		<pubDate>Tue, 31 Jul 2007 13:17:59 +0000</pubDate>
		<guid isPermaLink="false">http://healyourchurchwebsite.com/2007/07/20/dont-write-vague-use-cases-write-concrete-specific-use-cases/#comment-3622</guid>
		<description>C&#039;mon Jeff ... business logic is business logic no matter which way you organize it ...

... and as someone who goes Agile/Extreme for a living, I can tell you that how one stacks and package the &#039;story&#039; aren&#039;t nearly as important as getting the story correct from an operational point of view.

After all, we&#039;re talking church web sites here - I&#039;d be glad just to have a stack of notecards that describe the desired process ... let alone call quaint those whom aren&#039;t staffed-up with geek teams working 8 hours a day to fix something.</description>
		<content:encoded><![CDATA[<p>C&#8217;mon Jeff &#8230; business logic is business logic no matter which way you organize it &#8230;</p>
<p>&#8230; and as someone who goes Agile/Extreme for a living, I can tell you that how one stacks and package the &#8216;story&#8217; aren&#8217;t nearly as important as getting the story correct from an operational point of view.</p>
<p>After all, we&#8217;re talking church web sites here &#8211; I&#8217;d be glad just to have a stack of notecards that describe the desired process &#8230; let alone call quaint those whom aren&#8217;t staffed-up with geek teams working 8 hours a day to fix something.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jdb1972</title>
		<link>http://healyourchurchwebsite.com/2007/07/20/dont-write-vague-use-cases-write-concrete-specific-use-cases/comment-page-1/#comment-3621</link>
		<dc:creator>jdb1972</dc:creator>
		<pubDate>Tue, 31 Jul 2007 12:55:15 +0000</pubDate>
		<guid isPermaLink="false">http://healyourchurchwebsite.com/2007/07/20/dont-write-vague-use-cases-write-concrete-specific-use-cases/#comment-3621</guid>
		<description>Use cases? How quaint. Agile/Extreme stories are the way to go.</description>
		<content:encoded><![CDATA[<p>Use cases? How quaint. Agile/Extreme stories are the way to go.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

