<?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: The Problem with Requirements Engineering tools</title>
	<atom:link href="http://blog.nwcadence.com/2007/11/the-problem-with-requirements-engineering-tools/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.nwcadence.com/2007/11/the-problem-with-requirements-engineering-tools/</link>
	<description>Thoughts on TFS, Lean, Agile, Kanban, Scrum and other collaborative technologies and techniques</description>
	<lastBuildDate>Tue, 07 Feb 2012 12:44:48 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: JayCharly</title>
		<link>http://blog.nwcadence.com/2007/11/the-problem-with-requirements-engineering-tools/comment-page-1/#comment-114</link>
		<dc:creator>JayCharly</dc:creator>
		<pubDate>Sun, 04 Apr 2010 05:36:54 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nwcadence.com/2007/11/16/the-problem-with-requirements-engineering-tools/#comment-114</guid>
		<description>I think there&#039;s a misconception about requirements management here. RM is not about gathering better requirements, it is about managing the requirements life-cycle so that creation, removal, updating and deletion operations are performed in an organized and controlled way. Therefore, anyone who uses an RM tool should not expect to improve the internal quality of the requirements produced.
I agree with you about encouraging the development of communicative skills in order to promote a better understanding between analysts and stakeholders when eliciting requirements.</description>
		<content:encoded><![CDATA[<p>I think there&#8217;s a misconception about requirements management here. RM is not about gathering better requirements, it is about managing the requirements life-cycle so that creation, removal, updating and deletion operations are performed in an organized and controlled way. Therefore, anyone who uses an RM tool should not expect to improve the internal quality of the requirements produced.<br />
I agree with you about encouraging the development of communicative skills in order to promote a better understanding between analysts and stakeholders when eliciting requirements.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan Babcock &#187; Blog Archive &#187; The Business Analysis &#8220;Artist&#8221; and the Requirement Tools of the Trade</title>
		<link>http://blog.nwcadence.com/2007/11/the-problem-with-requirements-engineering-tools/comment-page-1/#comment-82</link>
		<dc:creator>Jonathan Babcock &#187; Blog Archive &#187; The Business Analysis &#8220;Artist&#8221; and the Requirement Tools of the Trade</dc:creator>
		<pubDate>Fri, 14 Nov 2008 03:53:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nwcadence.com/2007/11/16/the-problem-with-requirements-engineering-tools/#comment-82</guid>
		<description>[...] wanted to share and comment on a post I came across the other day that points out the potential drawback of requirements management tools. Per Jeff Levinson at Northwest Cadence: There seems to be a growing move towards using tools [...]</description>
		<content:encoded><![CDATA[<p>[...] wanted to share and comment on a post I came across the other day that points out the potential drawback of requirements management tools. Per Jeff Levinson at Northwest Cadence: There seems to be a growing move towards using tools [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Requirements are not dead. :: Where Technology Meets Teamwork</title>
		<link>http://blog.nwcadence.com/2007/11/the-problem-with-requirements-engineering-tools/comment-page-1/#comment-78</link>
		<dc:creator>Requirements are not dead. :: Where Technology Meets Teamwork</dc:creator>
		<pubDate>Sun, 09 Nov 2008 23:39:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nwcadence.com/2007/11/16/the-problem-with-requirements-engineering-tools/#comment-78</guid>
		<description>[...] has written about this problem and others in several blog posts, most noticably in his post on the problems of Requirements Engineering tools.  It&#8217;s also a very frequent discussion over the water cooler here at Northwest Cadence.  [...]</description>
		<content:encoded><![CDATA[<p>[...] has written about this problem and others in several blog posts, most noticably in his post on the problems of Requirements Engineering tools.  It&#8217;s also a very frequent discussion over the water cooler here at Northwest Cadence.  [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

