Agile Manager [EOL] vs Rally Software comparison

"How you write your user stories, and the requirements gathering, in Agile Manager is pretty good."

"CA Agile Central helps the entire organization run like one powerful team."

"It's a good platform to keep track of all the user stories across all projects. So rather than having one off Excel spreadsheets with all of the requirements, it is a good place to have all of that."

"The visibility it brings to the plan, the ability to capture tasks, and trace them all the way through the life cycle. Providing that visibility helps both me and the team, or teams, to be able to understand where we are in the development process."

"It documents stories in a way where we do not have to be heavy on front-end requirements, front-end documentation, and front-end workflows."

"Gives me a dashboard where I can see what things are not being worked on, what things are blocked."

"With this product, searching for historical information or the evolution of the requirement, detecting conflict between projects has helped a lot."

"We use Rally Software extensively in our agile development processes. We have program boards set up where we write and break down stories. We assign story points and map dependencies between different stories, showing how stories from one team may depend on stories from another team."

"The metrics - collecting metrics. It's because we've used several other tools in the past, and they don't give you a full indication of how well your teams are performing, at a portfolio level, at a product level, and at the team level."

"The testing module that we are used to, that wasn't there at all."

"What I don't like about it is that it is really hard to find old work to reference information and use the reporting section of the application in terms of trying to analyze trends. If I am trying to find out which interfaces took this long and I want to compare and measure improvement from one quarter to another quarter, the reporting mechanism within Rally is very troublesome. They have an Excel plugin that you're supposed to use, but you literally have to pull the raw data out before you can do the analysis. You can't do it within Rally, and if you can, it is a secret, and I don't know how to do it. It should have better, easier, and user-friendly reporting without having to use the Excel add-in. It is very clunky. There is a lot of data in there, but it is not organized in such a way that makes it intuitive. You really have to kind of look for where do you put your documentation or dates. Some customization is available, but it is not plug-and-play like Jira. When I switched from TFS to Jira, I just went and started using Jira, whereas with Rally, you kind of have to really get in and figure out what you need to do before you set stuff up, or you're going to get yourself stuck. You can just start using Jira and be successful."

"I'd like the ability to customize reports without having to incur Professional Services, or having to write my own code GitHub and then implement that as a custom report. That's untenable. It's not sustainable."

"It is hard to track the changes. For example, we're in sprint 25, and then we have 26, 27, 28, and 29. Throughout that whole time, we're developing pipelines in Azure, moving to GitHub, creating pipelines, and working with teams. But sometimes, we need to revisit specific decisions made in previous sprints, like pipeline details. Maybe it's in our Azure Wiki, GitHub, or Teams, but it's not always consistent. I wish I could search for all tasks or stories related to that particular effort without needing to know everyone's individual stories or features."

"There's a lot of support for Scrum and Agile, but it needs something for the Kanban side."

"We'd like better dashboards to make visibility better."

"From a test management perspective, it should have the capability to give you both automation and manual integration in one place."

"The navigation within the tool sometimes is a little tricky for me. I'm sure with more use, more practice, I'll become accustomed to it, but some of the things just aren't intuitive."

"As it is right now, it does not support automation of the quality assurance process. It just supports manual testing."

"Rally Software costs $50 a month, and for a base account, that price is acceptable."

"From a price point, it's a cost effective solution for our needs."

"It is expensive and may not be worthwhile for a small company."

"I don't know the exact pricing, but I think the tool is priced high. They provide quality workmanship, good software, regular upgrades, and they're always attentive and listen to users. Everything comes with a price. I think it's an expensive solution compared to Jira or other competitors, but it's a complete package."

"The license costs are fairly high as compared to some of the other solutions out there."

"Frankly, pricing is expensive and needs to be carefully planned for when budgeting."

"We are always looking for a discount, if the solution was less expensive it would be a benefit."

"I understand it's a little more expensive. That is why many people prefer Jira."