<?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: In defense of the humble spreadsheet</title>
	<atom:link href="http://mavericktester.com/in-defense-of-the-humble-spreadsheet/feed" rel="self" type="application/rss+xml" />
	<link>http://mavericktester.com/in-defense-of-the-humble-spreadsheet</link>
	<description>The startup&#039;s software tester</description>
	<lastBuildDate>Tue, 13 Jul 2010 23:47:40 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Anne-Marie</title>
		<link>http://mavericktester.com/in-defense-of-the-humble-spreadsheet#comment-617</link>
		<dc:creator>Anne-Marie</dc:creator>
		<pubDate>Wed, 20 May 2009 07:24:02 +0000</pubDate>
		<guid isPermaLink="false">http://mavericktester.com/?p=153#comment-617</guid>
		<description>&lt;a href=&quot;#comment-616&quot; rel=&quot;nofollow&quot;&gt;@Norvitz&lt;/a&gt; 
Thanks for the comment Norvitz, It looks similar to the Zephyr approach except perhaps less expensive. 
Unfortunately, it doesn&#039;t suit my purposes as I consult to small companies who would be unable to see defects after I left, unless they paid for extra user licenses. As most of the companies I deal with are small, its an overhead I don&#039;t want to put on them. 
I am looking into alternative approaches at the moment, such as hosting testlink on my webserver and then allowing access per project.</description>
		<content:encoded><![CDATA[<p><a href="#comment-616" rel="nofollow">@Norvitz</a><br />
Thanks for the comment Norvitz, It looks similar to the Zephyr approach except perhaps less expensive.<br />
Unfortunately, it doesn&#8217;t suit my purposes as I consult to small companies who would be unable to see defects after I left, unless they paid for extra user licenses. As most of the companies I deal with are small, its an overhead I don&#8217;t want to put on them.<br />
I am looking into alternative approaches at the moment, such as hosting testlink on my webserver and then allowing access per project.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Norvitz</title>
		<link>http://mavericktester.com/in-defense-of-the-humble-spreadsheet#comment-616</link>
		<dc:creator>Norvitz</dc:creator>
		<pubDate>Wed, 20 May 2009 06:39:46 +0000</pubDate>
		<guid isPermaLink="false">http://mavericktester.com/?p=153#comment-616</guid>
		<description>That&#039;s the reason we&#039;re using Practitest - which is SaaS. 
This means that there is no need to install configure or maintain. You just need to login and work. Still you have the benefits of a Test Management tool, like reports, coverage, etc.</description>
		<content:encoded><![CDATA[<p>That&#8217;s the reason we&#8217;re using Practitest &#8211; which is SaaS.<br />
This means that there is no need to install configure or maintain. You just need to login and work. Still you have the benefits of a Test Management tool, like reports, coverage, etc.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
