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."
"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."
"Good for managing stories, sprints, hydration and releases."
"All of the features work together to provide a powerful holistic solution - from the dashboard all the way through to security."
"The Defect feature. In one view you can see all your defects and you can push them into the different releases."
"It's designed around Agile, so it has all of the pieces that match up with the process."
"The most useful part is how it breaks down tasks into parents and children, manageable tasks. It has a whole project as an initiative, and then it breaks it down further and further. And then you get to actual user stories and tasks that you can sit and develop."
"With this product, searching for historical information or the evolution of the requirement, detecting conflict between projects has helped a lot."
"Helps me determine how fast I can launch, go to production."
"CA Agile Central helps the entire organization run like one powerful team."
"The configurable Portfolio Management and parent-child relationships."
"What I like most about Rally Software, in terms of using it for the agile process, is that it's clear, useful, and user-friendly. I also like that it has every field you can use for the Scrum process."
"Lacks ability to customize and reporting can be slow."
"The solution is very heavily vendor dependent."
"Some administrative tasks are difficult to perform. These could be simplified."
"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."
"Teams need clearer pictures of resource availability in charts and dashboards along with plans."
"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."
"The Reporting feature can improve, especially around executive summaries and dependency mapping."
"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."
"We'd like better dashboards to make visibility better."
"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."
"I would like to see more Kanban support. As it stands, it doesn't seem to have the features or the layouts that the teams really need to be able to execute their tasks. It almost tries to force you into more of a Scrum style."
"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."
"The product needs to have more integration capabilities."
More IBM Engineering Workflow Management Pricing and Cost Advice →
IBM Engineering Workflow Management is ranked 10th in Enterprise Agile Planning Tools with 1 review while Rally Software is ranked 7th in Enterprise Agile Planning Tools with 7 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 "Good discussion and note-taking capabilities but hard to track the changes". IBM Engineering Workflow Management is most compared with Jira, Microsoft Azure DevOps, Codebeamer, 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.