We performed a comparison between IBM Engineering Workflow Management and Rally Software based on real PeerSpot user reviews.
Find out what your peers are saying about Microsoft, GitLab, Atlassian and others in Enterprise Agile Planning Tools."Traceability reporting is inbuilt and includes all your requirements."
"Good for managing stories, sprints, hydration and releases."
"Agile templates give us a standard methodology for every Agile project. Also, the ability to create our own object types and linkages to features/epics allows us to enhance the verification of feature readiness."
"We can track the status of test cases (passed or saved) in a single view. Based on releases and other attributes, we generate various reports and extract metrics from the data."
"Work distribution among team members and accountability for completion with a clearer picture."
"All of the features work together to provide a powerful holistic solution - from the dashboard all the way through to security."
"We use the roadmap features, and we're getting better at using dates to use the roadmap so that we can see if we're on target for work."
"Tech support is very responsive, helpful, and available."
"The product has excellent customizable reports."
"CA Agile Central helps the entire organization run like one powerful team."
"The reporting, and being able to roll that up across the verticals, was an important selling point for us."
"Helps me plan an estimate of how soon or how far out we'll be able to deliver something."
"Its ability to scale."
"Reporting is much easier and faster than Micro Focus ALM, with CA AC built on web services... Also, the data is more granular when it comes to tasks, iterations, sprints, and releases."
"Teams need clearer pictures of resource availability in charts and dashboards along with plans."
"Some administrative tasks are difficult to perform. These could be simplified."
"Lacks ability to customize and reporting can be slow."
"The solution is very heavily vendor dependent."
"We have encountered issues with stability. We have seen where the entire system kind of goes for a toss when certain people use certain types of queries, which are very costly. Then the system kind of slows down a bit, and we have to monitor it."
"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 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."
"I think the interface could be a little bit more visual and less wordy. Right now, it seems like it's just a lot of text on the page. In other ticketing systems where it's more visual, you can see more of a flow. But in this one it's more just a list of tasks. I would like to see that a little bit better, especially considering it has so many great organizational features, like child tasks, different artifacts. It would be great to see it presented more appropriately."
"We want Rally to generate OKRs, to allow teams to record the OKRs, and then the OKRs can be mapped to the epics and there is organizational alignment."
"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."
"One problem I see is that if there is a dependent user story - for example, if my team is working on one thing and there is a dependent user story from another team - we can have a dependency created but we don't know if there is a change of status from the other team. That is something which is very important for Agile Central to look into so that if the other team makes any changes we will be notified as well."
"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."
"In Rally Software, the connection with GitLab and GitHub needs improvement."
More IBM Engineering Workflow Management Pricing and Cost Advice →
IBM Engineering Workflow Management is ranked 10th in Enterprise Agile Planning Tools with 14 reviews while Rally Software is ranked 6th in Enterprise Agile Planning Tools with 116 reviews. IBM Engineering Workflow Management is rated 6.8, while Rally Software is rated 8.2. The top reviewer of IBM Engineering Workflow Management writes "Offers good traceability elements but UI needs improvement ". 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". IBM Engineering Workflow Management is most compared with Jira, Codebeamer, Microsoft Azure DevOps, GitLab and Polarion ALM, whereas Rally Software is most compared with Microsoft Azure DevOps, Jira, TFS, Jira Align and OpenText ALM / Quality Center.
See our list of best Enterprise Agile Planning Tools vendors.
We monitor all Enterprise Agile Planning Tools 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.