<?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: Analysis Paralysis and Agile Development</title>
	<atom:link href="http://tynerblain.com/blog/2007/08/30/analysis-paralysis/feed/" rel="self" type="application/rss+xml" />
	<link>http://tynerblain.com/blog/2007/08/30/analysis-paralysis/</link>
	<description>Software product success.</description>
	<lastBuildDate>Tue, 22 May 2012 20:46:27 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: Scott Sehlhorst</title>
		<link>http://tynerblain.com/blog/2007/08/30/analysis-paralysis/comment-page-1/#comment-143200</link>
		<dc:creator>Scott Sehlhorst</dc:creator>
		<pubDate>Mon, 03 Sep 2007 03:32:14 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2007/08/30/analysis-paralysis/#comment-143200</guid>
		<description>Hey guys, thanks as always for reading and commenting.

Rajeev - how has BA pairing worked for you on this?

David - definitely agree that timeboxing the requirements cuts this off at the knees too.  I just wish there were a &#039;one size fits all&#039; number we could use with a smaller time increment.  For example - &quot;spend 8 hours eliciting and writing a &#039;complex&#039; use case.&quot;  I think we can all apply limits like that, but there isn&#039;t a magic number we can say applies to everyone.</description>
		<content:encoded><![CDATA[<p>Hey guys, thanks as always for reading and commenting.</p>
<p>Rajeev &#8211; how has BA pairing worked for you on this?</p>
<p>David &#8211; definitely agree that timeboxing the requirements cuts this off at the knees too.  I just wish there were a &#8216;one size fits all&#8217; number we could use with a smaller time increment.  For example &#8211; &#8220;spend 8 hours eliciting and writing a &#8216;complex&#8217; use case.&#8221;  I think we can all apply limits like that, but there isn&#8217;t a magic number we can say applies to everyone.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave Wright</title>
		<link>http://tynerblain.com/blog/2007/08/30/analysis-paralysis/comment-page-1/#comment-142584</link>
		<dc:creator>Dave Wright</dc:creator>
		<pubDate>Sun, 02 Sep 2007 01:17:16 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2007/08/30/analysis-paralysis/#comment-142584</guid>
		<description>For me, its all about time, its the one resource you can&#039;t replace. So, we have the creation of the &quot;time-box&quot; (have to look up who first used the term and concept...). Get a scope agreed too, and then go to it for an also-agreed-to period of time; 4 weeks works for me. Presuming reasonable access to business SME&#039;s and no debilitating project constraints, anyone can deliver a whole lot of requirements in 4 weeks.</description>
		<content:encoded><![CDATA[<p>For me, its all about time, its the one resource you can&#8217;t replace. So, we have the creation of the &#8220;time-box&#8221; (have to look up who first used the term and concept&#8230;). Get a scope agreed too, and then go to it for an also-agreed-to period of time; 4 weeks works for me. Presuming reasonable access to business SME&#8217;s and no debilitating project constraints, anyone can deliver a whole lot of requirements in 4 weeks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rajeev Singh</title>
		<link>http://tynerblain.com/blog/2007/08/30/analysis-paralysis/comment-page-1/#comment-142005</link>
		<dc:creator>Rajeev Singh</dc:creator>
		<pubDate>Fri, 31 Aug 2007 23:07:35 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2007/08/30/analysis-paralysis/#comment-142005</guid>
		<description>BA Pairing prevents this from happening. Also, it is on the top of the agenda for an IM to make sure that the flow of stories/requirements is maintained.</description>
		<content:encoded><![CDATA[<p>BA Pairing prevents this from happening. Also, it is on the top of the agenda for an IM to make sure that the flow of stories/requirements is maintained.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

