Agile Manager [EOL] vs Rally Software comparison

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

"The most valuable feature is actually creating a field within there for architectural review. So when teams are struggling or have questions on the architecture or strategy that they take, they can actually flag that particular story, release, or project. Those can then be reviewed by the architecture team and the teams actually get additional information on how to course-correct, build on the architecture that we're trying to build throughout the organization, and get over road blocks much quicker."

"It helps with getting the alignment between strategy and execution for the product teams, all the way down to the delivery teams."

"We can work better and at a higher quality, than we were able to before."

"The tool is very useful for generating metrics to improve our project management. It helps with productivity by allowing us to focus on small pieces of functionality and deliver them in short timeframes. The tool provides senior management with visibility on priorities and progress."

"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."

"My teams uses it for their daily agile management. They describe their user stories and track the progress of their projects."

"Agile Central allows us to log one hundred percent of the work we do and it allows for no hidden work, so teams can't go under the radar with what they're working on."

"It's designed around Agile, so it has all of the pieces that match up with the process."

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

"In terms of improvement, perhaps some more metrics. If they could add some additional, that would be cool."

"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."

"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."

"The product needs to have more integration capabilities."

"Customization features may not be exposed or unavailable, so people may be looking for them. So, customization is an area people have told me is more desirable."

"The solution is expensive."

"It requires better scalability for the implementation of the whole suite. We do not use it in that fashion, and visibility is sometimes a problem."

"We did submit an enhancement request. I think a lot of teams that do very large scale products have the same issue. They just do not realize it would help them."

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

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

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

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

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

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

"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."

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