<?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: Traceability &#8211; Just Make it Simple.</title>
	<atom:link href="http://www.jamasoftware.com/blog/2008/05/15/traceability-just-make-it-simple/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.jamasoftware.com/blog/2008/05/15/traceability-just-make-it-simple/</link>
	<description>Our blog about software product development, requirements management and an inside look into our company.</description>
	<lastBuildDate>Sat, 18 Apr 2009 19:43:36 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Joy Beatty</title>
		<link>http://www.jamasoftware.com/blog/2008/05/15/traceability-just-make-it-simple/comment-page-1/#comment-25</link>
		<dc:creator>Joy Beatty</dc:creator>
		<pubDate>Wed, 28 May 2008 16:24:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.jamasoftware.com/blog/2008/05/15/traceability-just-make-it-simple/#comment-25</guid>
		<description>I think you&#039;ve posted a great question Eric! I think most people find it to be more trouble then value it adds. That said, the key is definitely in doing &quot;just enough&quot; and using a tool. For example, I&#039;ve worked on projects where if they had just traced the functionality back to business objectives, they would be light years ahead...but they didn&#039;t really do that well and so the team couldn&#039;t prioritize the work well. And there was no tool in play at the time.

Awhile back we had a similar discussion on this topic found here if you&#039;d like to read more:
http://www.seilevel.com/messageboard/showthread.php?t=569&amp;highlight=traceability</description>
		<content:encoded><![CDATA[<p>I think you&#8217;ve posted a great question Eric! I think most people find it to be more trouble then value it adds. That said, the key is definitely in doing &#8220;just enough&#8221; and using a tool. For example, I&#8217;ve worked on projects where if they had just traced the functionality back to business objectives, they would be light years ahead&#8230;but they didn&#8217;t really do that well and so the team couldn&#8217;t prioritize the work well. And there was no tool in play at the time.</p>
<p>Awhile back we had a similar discussion on this topic found here if you&#8217;d like to read more:<br />
<a href="http://www.seilevel.com/messageboard/showthread.php?t=569&amp;highlight=traceability" rel="nofollow">http://www.seilevel.com/messageboard/showthread.php?t=569&amp;highlight=traceability</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
