Azure DevOps Server vs. IBM Engineering Lifecycle Management

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Azure DevOps Server
Score 8.3 out of 10
N/A
AzureDevOps Server (formerly Team Foundation Server, or TFS) is a test management and application lifecycle management tool, from Microsoft's Visual Studio offerings. To license Azure DevOps Server an Azure DevOps license and a Windows operating system license (e.g. Windows Server) for each machine running Azure DevOps Server.N/A
IBM Engineering Lifecycle Management
Score 6.8 out of 10
N/A
IBM Engineering Lifecycle Management (ELM) is an end-to-end engineering solution used to manage system requirements to design, workflow, and test management, extending the functionality of ALM tools for better complex-systems development.N/A
Pricing
Azure DevOps ServerIBM Engineering Lifecycle Management
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Azure DevOps ServerIBM Engineering Lifecycle Management
Free Trial
NoNo
Free/Freemium Version
NoNo
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
Azure DevOps ServerIBM Engineering Lifecycle Management
Considered Both Products
Azure DevOps Server

No answer on this topic

IBM Engineering Lifecycle Management
Chose IBM Engineering Lifecycle Management
JIRA is simpler and much more intuitive, especially when bundled with Confluence. TFS is obvious choice if working with Microsoft technologies and has superb API.
Top Pros
Top Cons
Best Alternatives
Azure DevOps ServerIBM Engineering Lifecycle Management
Small Businesses
GitHub
GitHub
Score 9.0 out of 10
Polarion ALM
Polarion ALM
Score 9.3 out of 10
Medium-sized Companies
AWS CodePipeline
AWS CodePipeline
Score 9.2 out of 10
Polarion ALM
Polarion ALM
Score 9.3 out of 10
Enterprises
AWS CodePipeline
AWS CodePipeline
Score 9.2 out of 10
Polarion ALM
Polarion ALM
Score 9.3 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
Azure DevOps ServerIBM Engineering Lifecycle Management
Likelihood to Recommend
8.3
(47 ratings)
8.8
(22 ratings)
Likelihood to Renew
10.0
(1 ratings)
8.0
(6 ratings)
Usability
8.7
(3 ratings)
2.1
(4 ratings)
Support Rating
8.4
(10 ratings)
5.0
(3 ratings)
Implementation Rating
8.0
(1 ratings)
10.0
(1 ratings)
Ease of integration
9.0
(2 ratings)
-
(0 ratings)
User Testimonials
Azure DevOps ServerIBM Engineering Lifecycle Management
Likelihood to Recommend
Microsoft
Azure DevOps is good to use if you are all-in on the Microsoft Azure stack. It's fully integrated across Azure so it is a point-and-click for most of what you will need to achieve. If you are new to Azure make sure you get some outside experience to help you otherwise it is very easy to overcomplicate things and go down the wrong track, or for you to manually create things that come out of the box.
Read full review
IBM
IBM Engineering Requirements Management DOORS former IBM Rational DOORS profits very much from the mighty market position it had till today. It had been the most favored requirement engineering tools suite with the highest investments in the infrastructure concerning hardware, software, and knowledge sources. It was embedded in knowledge sources of test stands, hardware labs, and knowledge database servers. It allowed for some of the highest profit changes and made the fame with it. But the paradigms of requirements engineering change. If not were superseded by completely different approaches for the target solution worlds. The foremost position in the selling tables is unstable if changes are not solved or coped with by the strategist at IBM and their customers. Since the highly successful alternative suits are already at the market, and some are from IBM already the lifecycle for IBM Engineering Requirements Management DOORS is at the later highs. But the suite is still at the very top and very popular. There are still many problems unsolved and many wishes at the customers to make the use more comfortable and efficient at the overall level. If the time of setting up the software package is passed the adoption get more extended and complicated. There is a lot of work at the stage around and the expertise will be required for a long time from now.
Read full review
Pros
Microsoft
  • Reporting Integration- Azure boards provides Kanban and other dashboard, their templates for easy management of project.
  • Project Pipeline- easy integration and development of CI/CD pipelines, helped in testing, releasing project artifacts.
  • Version Control- Integration with Git and code IDE made it easy to share, review our code, fix bugs and do testing.
Read full review
IBM
  • Easy to use with well defined template and user defined fields. New team can setup a project area easily by copying an existing template and adding customized fields for their special needs.
  • It can be used during almost the whole project cycle and give us a better view and control on the projects.
  • Lots of built-in report functions.
Read full review
Cons
Microsoft
  • Can add more build templates for specific technology requirements
  • Can have more features in dashboards which can help dev teams stream line their tasks and priorities
  • Can have raise alarm feature in case of any sort of failure in devops pipeline execution
Read full review
IBM
  • Wireframes are quite basic. If you need intuitive and interactive wireframes to elaborate the requirements. you probably need to define outside the tool and then upload as image.
  • ER (define data dictionaries) modeling is not there.
  • Use case modeling is quite basic. You can visualize the use case and actors relation but the tool does not enforce the rules.
  • Does not support offline work.
Read full review
Likelihood to Renew
Microsoft
Because we are a Microsoft Gold Partner we utilize most of their software and we have so much invested in Team Foundation Server now it would take a catastrophic amount of time and resources to switch to a different product.
Read full review
IBM
At the moment we are required by contract to continue to use the IBM DOORS software for our current client. Given that it can be expensive, if we were to use it after our current client's needs were met, we would have to secure other projects in order to justify the continued use of the software.
Read full review
Usability
Microsoft
Azure DevOps Server or TFS is a complete suite in itself. From Developer's machine where the code is developed to the production environment where the code is meant to run it take care of complete flow within itself. It acts as a code repository you can check-in check-out codes using GIT interface. It also acts as a Build and Automation Test tool which can help you to judge sanctity of your code. It further acts as a release manager to deploy your application to the production environment. And all these steps can also be performed without any manual intervention with the option to have approval processes. Hence its a perfect blend of all set of tools and capabilities required to bring code to production.
Read full review
IBM
The UI is terrible and not intuitive. Users need training in order to complete tasks. Much like SAP, it's not the clearest tool. The tracing feature is especially complicated because you must write the scripts yourself. There is a learning curve. Also, even the setup, installation, and logging in each time takes a considerable amount of time.
Read full review
Support Rating
Microsoft
I have not had to use the support for Azure DevOps Server. There have never been any issues where I was not able to figure it out or quickly resolve. Our Scrum Master has used support before though, and the service has always been prompt and clear with a customer-focus
Read full review
IBM
It does a basic job and has the potential to complete some robust reporting tasks, however, it really is a clunky piece of software with a terrible user interface that makes using it routinely quite unpleasant. Many of our legacy and maintenance projects still use DOORS but our department and company use many alternatives and are looking for better tools.
Read full review
Implementation Rating
Microsoft
Do research beforehand and, if possible, do a trial run before implementing into production environment.
Read full review
IBM
No problems
Read full review
Alternatives Considered
Microsoft
In my opinion, DevOps covers the development process end to end way better than Jira or GitHub. Both competitors are nice in their specific fields but DevOps provides a more comprehensive package in my opinion. It is still crazy to see that the whole suite can be used for free. The productivity increase we realized with DevOps is worth real money!
Read full review
IBM
It was easier to do all the change management-related activities, even configurations were handled very effectively. New process definitions and initiatives made it easier for better project deliverables. Effective resource allocations and better reporting and defect management. The overall cost of the tool is great too and well within budget.
Read full review
Return on Investment
Microsoft
  • It has streamlined the pipeline and project management for our agile effort.
  • It has helped our agile team get organized since that is a new methodology being leveraged within the Enterprise.
  • The calendar has improved visibility into different OOOs across the project team since we all come from different departments across the larger organization.
Read full review
IBM
  • If you can setup DOORS to your project, you will experience lower costs.
  • Also, less rework in the project, which means lower times to achieve your milestones.
  • Finally, the cost of setting up a related project is considerably lower, and the estimates obtained in the process are much more precise.
Read full review
ScreenShots