Rally Software vs. SpiraPlan

If your organisation is planning to adopt Scaled Agile Framework Methodology (SAFe) without being worried about cost, CA Agile Central is one of the best tools. Here, you can look at various release trains and how that then flows up to the overall program budget. You can look holistically across all the release trains with minimal effort and have it flow up to the program office’s budget. It also helps by easily maintaining backlogs and integrating more seamlessly into software developers releases, iterations, and features. It has no conformance issue as it supports almost all the browsers like IE from version 8.0, Firefox from 3.6 and the newest versions of Chrome (from 6.0) and Safari (from 4.0).

We selected SpiraPlan because the workflow allows us to start simple without adopting an entire methodology. It suits small teams and single users really well.

• structuring teams separately in a clean way. You can add as much teams as you want, and guarantee each team's work would stay separate in browsing, graphs and analytics.
• detailed menus and drop-downs listing of features - technically it covers all there is of agile aspects and some more
• ability to set your email notifications on/off
• ability to split user stories into the next iteration if work isn't done in the previous one - no need to duplicate your user story manually

Incentivized

• Flexible requirements organisation structure. I'm able to group and sub-group requirements as I see fit.
• Competitive product pricing. Paying by active use instead of registered user was the winning point.
• UI is straightforward and easy to use.

• It is overly complicated in some views.
• Project Filtering seems buggy. Pinning a project does not always seem to help. Seems to default back to previous projects.
• Whereas it is great for project reporting, it is not nearly as easy as Jira for devs to use.

• Access from South East Asia is rather sluggish. Could be due to server location.
• Complimentary phone app to do simple tasks (e.g. create tasks, create requirements, add comments) offline would be beneficial because access to the internet can be an issue at the customer's environment.

Assuming we were paying - right now my group gets it for free as the broader engineering organization pays for it. There would be switching costs. There would be pretty minimal data migration, but the biggest cost is getting people to learn a new tool and starting off on the right footing. Evaluation and identification of the right product is a big part of switching too

Great UI, recent refresh was terrific. Great graphs and metrics, inline editing for updates, and a multitude of views on sprint progress make for a great team collaboration experience. There is also an active community and forums so that if you do need help, it is readily available

Don’t recall ever being unavailable.

The screens render relatively quickly but many actions that you would expect to require a single click require multiple clicks and pop-up windows. The extra windows and clicks make the product feel ponderous.

I've had to use support only one time and my issue was eventually resolved but not because of my ticket--because others complained about the functionality taken away so they brought it back. My ticket was never answered or addressed. So I can't really say much for the support factor for Rally.

Incentivized

It more or less confirmed that we are using it the way they had in mind. We were hoping for a epiphany in terms of how we could use it better.

They also want to be a go to source for agile processes and have an online resource center. It’s not that great but had a couple of nuggets. It hasn’t really helped us too much and we are not too far off from the classical interpretation of agile.

I would recommend training, in particular for organizations that multiple on-going projects. The product seems optimized for larger, more complex teams and getting proper training on how to configure, administer and use the system would be beneficial

Implementation of RALLY services and program satisfaction among various group,... 1) Dev Outcomes: How were our resiliencies, development, learning & practitioners “make them do the work,” but that they ask you to do it “in a way like before. 2) The Ops group: Just wish to make sure any change won't break current production envirements All the stake holders has to be on the same page

Incentivized

Rally and Asana have comparable features and are both valuable project management tools, but Asana's user interface is well-organized and highly intuitive. It's easy to add tasks and collaborators, edit due dates, indicate progress on tasks, close out projects, etc. However, Rally's interface is somewhat cluttered and difficult to navigate. My team ended up choosing Asana over Rally due to these concerns.

Incentivized

Main differentiating factors: 1. Lightweight process 2. Plans based on active users instead of registered users.

• Moving from Waterfall to Scrum or Kanban has been a big win for us. The adaptability and customization of CA Agile Central has aided in our success.
• Agile methodologies and CA Agile Central has made it easier to integrate business product owners into an agile team.

Incentivized

• Allows us to manage simple IT requirements without major upfront costs. Allows us to expand our process complexity at our own pace.
• Slow UI response from a South East Asia country can make data entry a drag.