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."Traceability reporting is inbuilt and includes all your requirements."
"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."
"Work distribution among team members and accountability for completion with a clearer picture."
"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."
"Its visual display and ease of use are most valuable."
"We like team collaboration and cross-functional collaboration."
"The most valuable features of this solution are workflow and reporting."
"One of the valuable features is traceability from requirements to test cases."
"We love the bulk edit feature. Jira also integrates well with Bitbucket."
"I have found Jira to be stable."
"The UI is good. It's simple and not very complicated. It's very good for tracking."
"Workflow administration is an easy process, especially with respect to defects."
"With this product, searching for historical information or the evolution of the requirement, detecting conflict between projects has helped a lot."
"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."
"Helps me determine how fast I can launch, go to production."
"Rally Software provides the capability to accurately estimate the time required for building large software projects, which can be challenging to predict...Rally Software enables us to schedule tasks better, allocate resources, and meet project deadlines."
"It is very stable. It has been on the market a long time."
"It scales very well. It improves in technology constantly and gets up to speed with the latest and greatest."
"The most valuable features of Rally Software are the executive dashboards, ease of use, and many other features. They have encapsulated everything that a GI can do, such as monitoring, maintaining, and then releasing. It's continuous integration and development."
"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."
"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."
"The solution is very heavily vendor dependent."
"Some administrative tasks are difficult to perform. These could be simplified."
"Lacks ability to customize and reporting can be slow."
"Some of the interfaces, especially on the administrator side and for permissions, are not so clear. They aren't very user-friendly."
"A more organized hierarchy is important. Reporting and JQL create issues for me. They do not completely cover the reporting part that I need to report in terms of my capacity to plan. In the same token, there is no record at this very moment to provide me with one export with epics story points, tasks, or issues and their sub-tasks at the same time."
"The solution needs more integrations with Azure DevOps OnPrem."
"They are not supporting in-house servers anymore and I think I've got until January to port this to something else."
"Workflows can be improved. We don't use workflows because we can't handle that much complexity. Its interface could be more intuitive for workflows."
"Some small issues with stability."
"So at one point in time, they did a huge UI upgrade. At that time, I felt like they had changed something, so it was hard to figure out. Now that we are habituated, it's not an issue now."
"Tracking is important but the built-in features don't meet our needs."
"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."
"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."
"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."
"The Reporting feature can improve, especially around executive summaries and dependency mapping."
"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."
"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."
"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."
"In Rally Software, the connection with GitLab and GitHub needs improvement."
More IBM Engineering Workflow Management Pricing and Cost Advice →