<?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: SW Development Lifecycle Tools Review</title>
	<atom:link href="http://onticoren.com/2008/02/19/sw-development-lifecycle-tools-review/feed/" rel="self" type="application/rss+xml" />
	<link>http://onticoren.com/2008/02/19/sw-development-lifecycle-tools-review/</link>
	<description>Enough virtual, it's time for something real by Oren Teich.</description>
	<lastBuildDate>Wed, 13 Jan 2010 21:28:48 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Agile Scrum</title>
		<link>http://onticoren.com/2008/02/19/sw-development-lifecycle-tools-review/comment-page-1/#comment-83</link>
		<dc:creator>Agile Scrum</dc:creator>
		<pubDate>Fri, 27 Jun 2008 12:46:59 +0000</pubDate>
		<guid isPermaLink="false">http://onticoren.com/2008/02/19/sw-development-lifecycle-tools-review/#comment-83</guid>
		<description>TargetProcess is also a very good tool</description>
		<content:encoded><![CDATA[<p>TargetProcess is also a very good tool</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ontic Oren &#187; Accept_360.version++; clean_up_interface();</title>
		<link>http://onticoren.com/2008/02/19/sw-development-lifecycle-tools-review/comment-page-1/#comment-66</link>
		<dc:creator>Ontic Oren &#187; Accept_360.version++; clean_up_interface();</dc:creator>
		<pubDate>Fri, 25 Apr 2008 05:39:25 +0000</pubDate>
		<guid isPermaLink="false">http://onticoren.com/2008/02/19/sw-development-lifecycle-tools-review/#comment-66</guid>
		<description>[...] move along.  But then, I am into version inflation.  Accept has always excelled at that &#8220;phase 1&#8221; task set.  The ability to cleanly trace requirements from customer input through to [...]</description>
		<content:encoded><![CDATA[<p>[...] move along.  But then, I am into version inflation.  Accept has always excelled at that &#8220;phase 1&#8221; task set.  The ability to cleanly trace requirements from customer input through to [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ontic Oren &#187; SW Development tools - Wiki &#38; Bugs</title>
		<link>http://onticoren.com/2008/02/19/sw-development-lifecycle-tools-review/comment-page-1/#comment-38</link>
		<dc:creator>Ontic Oren &#187; SW Development tools - Wiki &#38; Bugs</dc:creator>
		<pubDate>Sat, 22 Mar 2008 22:31:47 +0000</pubDate>
		<guid isPermaLink="false">http://onticoren.com/2008/02/19/sw-development-lifecycle-tools-review/#comment-38</guid>
		<description>[...] concluded the tools analysis that I kicked off a few weeks ago. What initially began as a look into requirements management tools quickly expanded into the entire [...]</description>
		<content:encoded><![CDATA[<p>[...] concluded the tools analysis that I kicked off a few weeks ago. What initially began as a look into requirements management tools quickly expanded into the entire [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Corey Trager</title>
		<link>http://onticoren.com/2008/02/19/sw-development-lifecycle-tools-review/comment-page-1/#comment-4</link>
		<dc:creator>Corey Trager</dc:creator>
		<pubDate>Fri, 29 Feb 2008 03:48:56 +0000</pubDate>
		<guid isPermaLink="false">http://onticoren.com/2008/02/19/sw-development-lifecycle-tools-review/#comment-4</guid>
		<description>If the KISS side of you wins out and you end up with FogBugz plus some wiki-to-be-named-later as your choice, then as a final step spend a few minutes maybe looking at &lt;a href=&quot;http://ifdefined.com/bugtrackernet.html&quot; rel=&quot;nofollow&quot;&gt;BugTracker.NET&lt;/a&gt;. 

Disclaimer: I&#039;m the author.

It&#039;s a free, open source app that draws some inspiration from FogBugz.   It&#039;s just an issue tracker.   No wiki.</description>
		<content:encoded><![CDATA[<p>If the KISS side of you wins out and you end up with FogBugz plus some wiki-to-be-named-later as your choice, then as a final step spend a few minutes maybe looking at <a href="http://ifdefined.com/bugtrackernet.html" rel="nofollow">BugTracker.NET</a>. </p>
<p>Disclaimer: I&#8217;m the author.</p>
<p>It&#8217;s a free, open source app that draws some inspiration from FogBugz.   It&#8217;s just an issue tracker.   No wiki.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Oren</title>
		<link>http://onticoren.com/2008/02/19/sw-development-lifecycle-tools-review/comment-page-1/#comment-3</link>
		<dc:creator>Oren</dc:creator>
		<pubDate>Fri, 29 Feb 2008 03:28:59 +0000</pubDate>
		<guid isPermaLink="false">http://onticoren.com/2008/02/19/sw-development-lifecycle-tools-review/#comment-3</guid>
		<description>Cool, I will definitely be contacting rymatech to check out featureplan!

The phases are the three outlined above - 
Phase 1 - CRM/Customer interface/collection
Phase 2 - Project Management
Phase 3 - Release management

I made these up based on my use of the tools and experience.  I&#039;m sure the lines are wrong. :)  I&#039;ve found that gathering customer feeback or requirements, and tracing that to the customer is very different from managing the individual use case and working with engineering, is very different from managing the bugs and working with the sustaining and customer facing activities.  

Comment, input, or suggestions on better ways to break down the space are greatly appreciated.</description>
		<content:encoded><![CDATA[<p>Cool, I will definitely be contacting rymatech to check out featureplan!</p>
<p>The phases are the three outlined above &#8211;<br />
Phase 1 &#8211; CRM/Customer interface/collection<br />
Phase 2 &#8211; Project Management<br />
Phase 3 &#8211; Release management</p>
<p>I made these up based on my use of the tools and experience.  I&#8217;m sure the lines are wrong. :)  I&#8217;ve found that gathering customer feeback or requirements, and tracing that to the customer is very different from managing the individual use case and working with engineering, is very different from managing the bugs and working with the sustaining and customer facing activities.  </p>
<p>Comment, input, or suggestions on better ways to break down the space are greatly appreciated.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stewart Rogers</title>
		<link>http://onticoren.com/2008/02/19/sw-development-lifecycle-tools-review/comment-page-1/#comment-2</link>
		<dc:creator>Stewart Rogers</dc:creator>
		<pubDate>Thu, 28 Feb 2008 21:38:28 +0000</pubDate>
		<guid isPermaLink="false">http://onticoren.com/2008/02/19/sw-development-lifecycle-tools-review/#comment-2</guid>
		<description>What did you mean by Phase 1 and Phase 2?  

As for FeaturePlan, so much has changed in the past year.  New pricing model makes it so much more affordable, On-Demand (all web-based) version available - integration to Rally and more vendors to come.  By far the leading Product Management solution out there.</description>
		<content:encoded><![CDATA[<p>What did you mean by Phase 1 and Phase 2?  </p>
<p>As for FeaturePlan, so much has changed in the past year.  New pricing model makes it so much more affordable, On-Demand (all web-based) version available &#8211; integration to Rally and more vendors to come.  By far the leading Product Management solution out there.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->