<?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: Rally vs VersionOne Agile Planning Tools</title>
	<atom:link href="http://www.garyallison.com/rally-vs-versionone-agile-planning-tools/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.garyallison.com/rally-vs-versionone-agile-planning-tools/</link>
	<description>Thoughts on Software Teams, Effective Leadership, and Technology Industry Trends</description>
	<lastBuildDate>Wed, 19 May 2010 21:05:27 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Sean</title>
		<link>http://www.garyallison.com/rally-vs-versionone-agile-planning-tools/comment-page-1/#comment-122</link>
		<dc:creator>Sean</dc:creator>
		<pubDate>Thu, 12 Nov 2009 14:28:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.garyallison.com/rally-vs-versionone-agile-planning-tools/#comment-122</guid>
		<description>Personally we used Rally here for about 4 months.  The buggy interface, lack of proper reporting and very little if any ways to customize the interface made us switch to Atlassian&#039;s Jira.  

Personally we don&#039;t use Greenhopper however with proper workflows we see our development process moving along nice and efficient.

As a previous user I would strongly recommend against using Rally and look at a more enterprise (reporting, proper/integrated time tracking ready tool.</description>
		<content:encoded><![CDATA[<p>Personally we used Rally here for about 4 months.  The buggy interface, lack of proper reporting and very little if any ways to customize the interface made us switch to Atlassian&#8217;s Jira.  </p>
<p>Personally we don&#8217;t use Greenhopper however with proper workflows we see our development process moving along nice and efficient.</p>
<p>As a previous user I would strongly recommend against using Rally and look at a more enterprise (reporting, proper/integrated time tracking ready tool.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex Elderfield</title>
		<link>http://www.garyallison.com/rally-vs-versionone-agile-planning-tools/comment-page-1/#comment-110</link>
		<dc:creator>Alex Elderfield</dc:creator>
		<pubDate>Wed, 15 Jul 2009 12:15:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.garyallison.com/rally-vs-versionone-agile-planning-tools/#comment-110</guid>
		<description>Hi Gary, 

As we are now in july 2009, can you give us a one year on update on how you got on with Rally. 

I&#039;m currently looking at a tool that will allow us to capture requirements, manage issues and plan across both multiple teams and multiple products and projects. 

I&#039;ve got one team of eight developers who develop a single product then use this to deliver multiple simultaneous client projects (normally 10-12 projects on the go at any one time). We run 2 week iterations but people with change pairs during an iteration and will switch between client projects (sometimes developing, sometimes capturing requirements and other times focused on QA). 

We also have a few teams of 3-4 people who tend to focus upon the development of individual products on a 3 week iteration cycle. 

We currently use a combination of whiteboards (with cards and stickies), excel, MS project, bugzilla and a wiki to capture, track and report on projects but we feel there may be a better way. Any suggestions? I&#039;m currently looking at Rally and Target Process.

rgds/alex</description>
		<content:encoded><![CDATA[<p>Hi Gary, </p>
<p>As we are now in july 2009, can you give us a one year on update on how you got on with Rally. </p>
<p>I&#8217;m currently looking at a tool that will allow us to capture requirements, manage issues and plan across both multiple teams and multiple products and projects. </p>
<p>I&#8217;ve got one team of eight developers who develop a single product then use this to deliver multiple simultaneous client projects (normally 10-12 projects on the go at any one time). We run 2 week iterations but people with change pairs during an iteration and will switch between client projects (sometimes developing, sometimes capturing requirements and other times focused on QA). </p>
<p>We also have a few teams of 3-4 people who tend to focus upon the development of individual products on a 3 week iteration cycle. </p>
<p>We currently use a combination of whiteboards (with cards and stickies), excel, MS project, bugzilla and a wiki to capture, track and report on projects but we feel there may be a better way. Any suggestions? I&#8217;m currently looking at Rally and Target Process.</p>
<p>rgds/alex</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Stevens</title>
		<link>http://www.garyallison.com/rally-vs-versionone-agile-planning-tools/comment-page-1/#comment-103</link>
		<dc:creator>John Stevens</dc:creator>
		<pubDate>Thu, 18 Jun 2009 15:50:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.garyallison.com/rally-vs-versionone-agile-planning-tools/#comment-103</guid>
		<description>Thanks for the comparison.  It seems to me that Rally may is easier to learn out of the box, but VersionOne has greater capabilities if you put the time into it.  I was confused on what you said with multiple teams and multiple projects because that is our scenario and we use VersionOne&#039;s enterprise edition, which supports that.  Maybe you were looking at the &quot;team&quot; edition, which is for only 1 project.  The enterprise edition of VersionOne has a virtual whiteboard, dashboards, etc...so from a visibility standpoint, we are fine with a distributed team.  Am I missing something?</description>
		<content:encoded><![CDATA[<p>Thanks for the comparison.  It seems to me that Rally may is easier to learn out of the box, but VersionOne has greater capabilities if you put the time into it.  I was confused on what you said with multiple teams and multiple projects because that is our scenario and we use VersionOne&#8217;s enterprise edition, which supports that.  Maybe you were looking at the &#8220;team&#8221; edition, which is for only 1 project.  The enterprise edition of VersionOne has a virtual whiteboard, dashboards, etc&#8230;so from a visibility standpoint, we are fine with a distributed team.  Am I missing something?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Del Hager</title>
		<link>http://www.garyallison.com/rally-vs-versionone-agile-planning-tools/comment-page-1/#comment-78</link>
		<dc:creator>Del Hager</dc:creator>
		<pubDate>Wed, 10 Sep 2008 02:20:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.garyallison.com/rally-vs-versionone-agile-planning-tools/#comment-78</guid>
		<description>Thanks for your review of these agile development tools. I see that there are more tools available for the scrum process then there were 4 years ago. I am getting my agile team up and going here at PayPal and am looking for tools to support the scrum process with the team.</description>
		<content:encoded><![CDATA[<p>Thanks for your review of these agile development tools. I see that there are more tools available for the scrum process then there were 4 years ago. I am getting my agile team up and going here at PayPal and am looking for tools to support the scrum process with the team.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael</title>
		<link>http://www.garyallison.com/rally-vs-versionone-agile-planning-tools/comment-page-1/#comment-58</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Tue, 24 Jun 2008 19:08:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.garyallison.com/rally-vs-versionone-agile-planning-tools/#comment-58</guid>
		<description>Not sure whether you evaluated TargetProcess. It is comparable with other vendors and has some really nice ideas behind like process-per-team.</description>
		<content:encoded><![CDATA[<p>Not sure whether you evaluated TargetProcess. It is comparable with other vendors and has some really nice ideas behind like process-per-team.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
