We performed a comparison between IBM Engineering Workflow Management and Microsoft Azure DevOps based on real PeerSpot user reviews.
Find out in this report how the two Enterprise Agile Planning Tools solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."Good for managing stories, sprints, hydration and releases."
"The most valuable features of the solution are highly customizable reports and visibility for all the higher management."
"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."
"Traceability reporting is inbuilt and includes all your requirements."
"All of the features work together to provide a powerful holistic solution - from the dashboard all the way through to security."
"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."
"This platform provides a large span of tools and technologies."
"The most valuable feature of the solution is task management."
"The product is easy to use...It is a stable solution."
"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."
"It is easy to use. The shared repository is useful. Everything is in one environment."
"The most valuable feature is the ease of use and performance."
"The product is easy to use and very stable."
"It is good for the purpose it is designed for. It is good for maintaining a repository of application code, creating pipelines for deploying the code, building the code, and deploying the code. It can be easily used by developers. There are no issues."
"If you have multiple projects on one server, the tool becomes very slow, and some reports take longer to load."
"The solution is very heavily vendor dependent."
"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."
"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."
"Lacks ability to customize and reporting can be slow."
"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."
"The solution can improve by adding integration with on-premise tools. The only built-in repository options are GitHub and DevOps."
"Microsoft Azure DevOps could improve by providing better integration with other tools. It is very easy to integrate with Azure, but when you need to integrate with other solutions, such as Amazon Web Services, is difficult."
"There is room for improvement on the UI side, especially with merge requests. If we compare Azure DevOps to GitLab when it comes to branches and PRs (pull requests), GitLab has a better interface."
"They have to add more features such as schedules and more flexibility in the platform."
"The ability to extend work items was more flexible than it is now. Talking version control, one of our customers had some issues because they found it very difficult to manage more than 1000 repositories for one team project."
"The tool has a logical link between epic feature, user story, and task, but when you try to generate a report to show the delivery progress against a feature, it is not easy. To see the percentage completion for a feature or progress of any delivery, it is not easy to draw a report."
"There are some areas that need improvement such as tracking."
More IBM Engineering Workflow Management Pricing and Cost Advice →
IBM Engineering Workflow Management is ranked 10th in Enterprise Agile Planning Tools with 15 reviews while Microsoft Azure DevOps is ranked 1st in Enterprise Agile Planning Tools with 127 reviews. IBM Engineering Workflow Management is rated 6.8, while Microsoft Azure DevOps 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 Microsoft Azure DevOps writes "Allows us to deploy code to production without releasing certain features immediately and agile project management capabilities offer resource-leveling". IBM Engineering Workflow Management is most compared with Jira, Codebeamer, GitLab, Polarion ALM and Endevor, whereas Microsoft Azure DevOps is most compared with GitLab, Jira, TFS, Rally Software and ServiceNow Strategic Portfolio Management. See our IBM Engineering Workflow Management vs. Microsoft Azure DevOps report.
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.