<?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: Is Tool-Supported Test Management Profitable?</title>
	<atom:link href="http://www.beteoblog.com/2008/08/18/is-tool-supported-test-management-profitable/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.beteoblog.com/2008/08/18/is-tool-supported-test-management-profitable/</link>
	<description>Sustainability (not only) for Packaged Software Systems</description>
	<pubDate>Tue, 06 Jan 2009 06:32:27 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: beteo Successfully Assists SBB in Implementing HP Quality Center /// beteo</title>
		<link>http://www.beteoblog.com/2008/08/18/is-tool-supported-test-management-profitable/#comment-486</link>
		<dc:creator>beteo Successfully Assists SBB in Implementing HP Quality Center /// beteo</dc:creator>
		<pubDate>Wed, 10 Dec 2008 14:17:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.beteoblog.com/?p=94#comment-486</guid>
		<description>[...] SBB is utilizing HP Quality Center in its test environment, where standardized test procedures and consistent test management can now dramatically reduce software-related risks and improve testing [...]</description>
		<content:encoded><![CDATA[<p>[...] SBB is utilizing HP Quality Center in its test environment, where standardized test procedures and consistent test management can now dramatically reduce software-related risks and improve testing [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://www.beteoblog.com/2008/08/18/is-tool-supported-test-management-profitable/#comment-305</link>
		<dc:creator>John</dc:creator>
		<pubDate>Mon, 18 Aug 2008 17:43:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.beteoblog.com/?p=94#comment-305</guid>
		<description>nice article, we've found it valuable for tools to sync up requirements management with test management, so the traceability for tracking changes extends from requirements to use cases to test cases to defects, etc.  we did a recent survey with 200 software product teams and their main challenges were on the requirements phase of projects more so then QA/testing phase; you and your readers can download the full report here:  2008 state of requirements management report - http://www.jamasoftware.com/requirements_management_report_download.htm</description>
		<content:encoded><![CDATA[<p>nice article, we&#8217;ve found it valuable for tools to sync up requirements management with test management, so the traceability for tracking changes extends from requirements to use cases to test cases to defects, etc.  we did a recent survey with 200 software product teams and their main challenges were on the requirements phase of projects more so then QA/testing phase; you and your readers can download the full report here:  2008 state of requirements management report - <a href="http://www.jamasoftware.com/requirements_management_report_download.htm" onclick="javascript:pageTracker._trackPageview('/outbound/comment/http://www.jamasoftware.com/requirements_management_report_download.htm');" rel="nofollow">http://www.jamasoftware.com/requirements_management_report_download.htm</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
