Rally helped me to deliver successfully several projects for our customers.
September 03, 2019

Rally helped me to deliver successfully several projects for our customers.

Evgueny Lemasov | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User

Overall Satisfaction with Rally Software (formerly CA Agile Central)

On our projects, the distribution we use JIRA about 50% of the time, Rally 45%, and Microsoft TFS 5%. The choice depends on the different project features. I have personally used Rally Software and JIRA since 2009 and I would advise using Rally if you have serious budget requirements/restrictions for the project, you have a team of 5 to 20 developers (or several teams), and you know the release date.

The main advantage of the Rally is that on any day of the iteration, you know how many hours are in the "TO DO" column. Moreover, the fact that UI/UX of Rally is in a tabular form makes using this tool convenient for all project participants - from programmers, QA people and Scrum master to Product Owners and C level guys. You see all the important information on one page and you do not need to scroll.
  • Easy to set up, plan and estimate user stories.
  • Easy track hours and update "to do" hours.
  • Iteration Burn Down report is the best.
  • Project development process is standard for all teams and customers.
  • Rally Software monthly price for user is a little bit expensive.
  • It is a little bit hard to set up relation between Epic stories vs Child US.
  • Search by text is hard when you have a 2-3 year old project.
  • Rally Software allows us to understand what was done and how much time & labor was in every task of your project.
From my point of view It is more convenient than other PM tools. You see a lot on one screen without scrolling and can easily understand where you have problems on your project
Never had any problems.
It is perfect when:
  • You need to track and improve velocity
  • You have a budget and you must control time
  • Requirements are changing often
  • Requirements are changing in the middle of the iteration
  • You have to organize the work of developers and QA simultaneously