We performed a comparison between Microsoft Azure DevOps and Rally Software based on real PeerSpot user reviews.
Find out in this report how the two Application Lifecycle Management (ALM) Suites solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The most valuable feature of this solution is that it saves time."
"It is possible to add third-party extensions to increase the usability of the product."
"The most valuable feature is the ease of use and performance."
"I like the fact that there is built-in Power BI. Both are Microsoft tools. So, you can incorporate dashboard capabilities."
"The automated bill feature is most valuable. As with most software developers, I can build code on my machine, but if one of my coworkers can't build the same code on theirs, there are always issues in trying to track it down. The automated bill process makes it a lot easier to track down where the issues are and find out what bugs aren't being included for whatever reason."
"Setting up Azure DevOps was straightforward. It's easy to use the default templates. Everything is under our control, so it's simple to implement new requirements."
"Some of the valuable features are the functionality and the wide range of capabilities."
"Monitoring is most valuable."
"It allows us to work in a more dynamic fashion and track more of the development lifecycle."
"Tech support is very responsive, helpful, and available."
"Ease of use - I don't even know when a new release is coming and I don't need to because it's so easy to use what's new."
"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's very user-friendly."
"When it comes to the valuable features of Rally Software, it excels at burn-down charts, burn-up charts, and road mapping once it's set up. I particularly appreciated the new feature for releases and road mapping, which worked exceptionally well."
"Gives me a dashboard where I can see what things are not being worked on, what things are blocked."
"The effect of these kind of tools drives the way you organize things. It helps you shape the way you flow."
"We are facing some problems because the capacity can only be measured within a project. It cannot be measured across multiple projects. So, the reporting needs to be enhanced, and there should be more graphs to be able to easily give the upper management insights about all the employees from different departments. It will be helpful for employee management. Currently, the managers over here are using Power BI for insights because the functionality of Azure DevOps Boards is not enough. So, we have to export the data into another visualization tool and get the results."
"I can't think of any specific things at the moment, but I've run into things that I didn't like. I came across something that I wanted to be changed in DevOps, but I can't remember what it was. It was a particular feature I was looking for that I couldn't find."
"Improving the metrics that are readily available on the dashboard would be very helpful."
"The optimization feature in Microsoft Azure DevOps needs improvement. Control over multiple projects could also be improved."
"We did have some brief performance issues, however, that was due to putting everything on one epic instead of breaking a project up."
"The price could be lowered. It would be nice if it was cheaper."
"I would like to see better integration and collaboration between tools."
"As for room for improvement, more features need to be added to the classic pipeline. The build and release pipelines are present, but there has not been much improvement there."
"It's a bit cumbersome to manage the Project Picker. As we sunset teams or projects close out - but we still have test cases tied to those teams or projects that are being used in other spaces - we have this monstrous list in the Project Picker that becomes really difficult to manage and find, and we can't clean that up ourselves. It would be nice if it was easier to do that and not lose your history."
"I'd like to be able to color code timeboxes, so I have an easy visual way to track the success of sprints."
"We would like more meaningful, customizable dashboards."
"A lot of the features that we would be looking to add, I am learning may not be within Agile Central, but part of another CA tool set."
"I think there needs to be some simplification. The team-level side can be challenging and complicated."
"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 would like for workspace admins to be able to hide projects in the Project Picker and not lose any historical data; make them invisible to certain users, visible to certain users, depending on permission sets. That would be lovely."
"It could improve by being self-organizing: user stories, different hierarchies, and different perspectives. Not just as a single hierarchical structure, but something that can be multidimensional."
Microsoft Azure DevOps is ranked 2nd in Application Lifecycle Management (ALM) Suites with 127 reviews while Rally Software is ranked 7th in Application Lifecycle Management (ALM) Suites with 116 reviews. Microsoft Azure DevOps is rated 8.2, while Rally Software is rated 8.2. The top reviewer of Microsoft Azure DevOps writes "Allows us to deploy code to production without releasing certain features immediately and agile project management capabilities offer resource-leveling". On the other hand, the top reviewer of Rally Software writes "A solution that enables users to accurately estimate the time required for building large software projects". Microsoft Azure DevOps is most compared with GitLab, Jira, TFS, ServiceNow Strategic Portfolio Management and OpenText ALM / Quality Center, whereas Rally Software is most compared with Jira, TFS, Jira Align, OpenText ALM / Quality Center and GitLab. See our Microsoft Azure DevOps vs. Rally Software report.
See our list of best Application Lifecycle Management (ALM) Suites vendors and best Enterprise Agile Planning Tools vendors.
We monitor all Application Lifecycle Management (ALM) Suites reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
