<?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"
	>
<channel>
	<title>Comments on: Empowering Agile Development with CaliberRM</title>
	<atom:link href="http://blog.excastle.com/2005/11/10/empowering-agile-development-with-caliberrm/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.excastle.com/2005/11/10/empowering-agile-development-with-caliberrm/</link>
	<description>Life, .NET, and Cats</description>
	<pubDate>Thu, 28 Aug 2008 02:36:01 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: A Couple Questions</title>
		<link>http://blog.excastle.com/2005/11/10/empowering-agile-development-with-caliberrm/#comment-5436</link>
		<dc:creator>A Couple Questions</dc:creator>
		<pubDate>Mon, 17 Apr 2006 16:13:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.excastle.com/2005/11/10/empowering-agile-development-with-caliberrm/#comment-5436</guid>
		<description>As someone experienced with Caliber and familiar with Agile, I wanted to ask a couple questions on this topic:&lt;br&gt;&lt;br&gt;1) What level of requirements granularity to maintain in Caliber?  For instance is each requirement element a User Story?  A story test?  My experience has led me to beleive that the more granular and/or hierachical your requirements tree is, the more difficult it is to maintin traceabaility and generate documentation.  Does this jive with your experience?&lt;br&gt;&lt;br&gt;2) What traceability from/to your requirements have you found most worth the effort to maintain?&lt;br&gt;&lt;br&gt;- Bill Lakenan&lt;br&gt;- bill@lakenan.net
</description>
		<content:encoded><![CDATA[<p>As someone experienced with Caliber and familiar with Agile, I wanted to ask a couple questions on this topic:</p>
<p>1) What level of requirements granularity to maintain in Caliber?  For instance is each requirement element a User Story?  A story test?  My experience has led me to beleive that the more granular and/or hierachical your requirements tree is, the more difficult it is to maintin traceabaility and generate documentation.  Does this jive with your experience?</p>
<p>2) What traceability from/to your requirements have you found most worth the effort to maintain?</p>
<p>- Bill Lakenan<br />
<br />- <a href="mailto:bill@lakenan.net">bill@lakenan.net</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
