We performed a comparison between IBM Engineering Workflow Management, Jira, 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.
"All of the features work together to provide a powerful holistic solution - from the dashboard all the way through to security."
"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."
"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."
"Work distribution among team members and accountability for completion with a clearer picture."
"Traceability reporting is inbuilt and includes all your requirements."
"It's really smart how they connected third-party vendors into their own marketplace. You can create and add apps. Anybody can do it."
"I was able to do real-time reports myself without having to wait for data import."
"Great for tracking my development team's productivity."
"It is very flexible, so we can do pretty much what we want with it."
"It provides very good visibility and traceability. You can clearly see each and every part of a process. It is also user-friendly and robust. It is working well, and there are a lot of add-ons or plug-ins out there that you can use."
"Offers a common language set so we can bring people into projects and get them up and running almost immediately."
"The roadmap feature and the ability to integrate with Power BI are probably the most valuable features in it. It is a great solution. I absolutely love it. It is a tool that was designed for project management, and it has been awesome to work with it so far. I also love Confluence."
"It is a very convenient tool. We can organize our sprints through scrum or kanban. There are scrum boards, and there are kanban boards. If you prefer scrum, you can use Jira. If you prefer kanban, you can still use Jira. You can create your kanban boards in a similar way as you create your scrum boards. It is very useful. It also seems to be very popular these days."
"The transparency it allows us to provide, both from the team level all the way through the executive level within the company and the work that we are doing."
"It helps with getting the alignment between strategy and execution for the product teams, all the way down to the delivery teams."
"The configurable Portfolio Management and parent-child relationships."
"We've actually used it for virtual PI planning. We have teams in different locations, and we actually virtually do PI planning, big-room planning, using the tools."
"My teams uses it for their daily agile management. They describe their user stories and track the progress of their projects."
"Helps me plan an estimate of how soon or how far out we'll be able to deliver something."
"CA Agile Central provides visibility into how teams are meeting business objectives."
"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."
"Lacks ability to customize and reporting can be slow."
"The solution is very heavily vendor dependent."
"Teams need clearer pictures of resource availability in charts and dashboards along with plans."
"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."
"Some administrative tasks are difficult to perform. These could be simplified."
"Could be more stable with more integrations."
"Whenever you edit a story, whatever you have changed takes a bit of time to save."
"One thing that I don't like about Jira is that when you do an export, it only allows a thousand issues. So the export feature needs to be better."
"A lot of the user interface could be updated."
"Jira should allow you to create and develop pipelines easily. In India, we have to purchase them separately or integrate other data tools. All these tools should be in Jira."
"I think that there is some ease of use that could be brought in to improve certain things."
"Not very intuitive for project admins."
"Reporting is something Jira could work on. The reporting capabilities should have the same flexibility we see in Excel, including the ability to manipulate data and create graphs. They need to have that, so we don't need to export to a spreadsheet."
"I think there is a missing link with the development activity. Some developers are pushing in new versions of the code, but you cannot make the link from the user story to a specific application version."
"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."
"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."
"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."
"The stronger CA can get on dependency mapping the better. That's the biggest hiccup. As you're setting up your features, they should make it easier to flag the dependencies, either across features or across projects. Then you're more set up for success."
"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."
"More importantly, we are seeing internal challenges from Atlassian because of their highly integrated suite that enables further automation and centralization of activities that are also highly necessary – messaging notifications cued off builds, collaboration on Solution Architecture Documentation, etc."
More IBM Engineering Workflow Management Pricing and Cost Advice →
