Azure DevOps (formerly VSTS, Microsoft Visual Studio Team System) is an agile development product that is an extension of the Microsoft Visual Studio architecture. Azure DevOps includes software development, collaboration, and reporting capabilities.
$2
per GB (first 2GB free)
IBM Engineering Lifecycle Management
Score 7.0 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 Services
IBM Engineering Lifecycle Management
Editions & Modules
Azure Artifacts
$2
per GB (first 2GB free)
Basic Plan
$6
per user per month (first 5 users free)
Azure Pipelines - Self-Hosted
$15
per extra parallel job (1 free parallel job with unlimited minutes)
Azure Pipelines - Microsoft Hosted
$40
per parallel job (1,800 minutes free with 1 free parallel job)
ADO is well suited for the visibility of day-to-day tasks and responsibilities as well as things such as Features, user stories, etc. Off the top of my head, I can't think of any scenario where it might not be well suited, as you can customize ADO to your liking to a degree.
While working on a complex project it is important all the needed change requests are handled in an effective manner, this tool helps us do exactly the same, it had great features to manage those change management tickets, making sure to merge the change with existing workflow, prioritize the requests centrally so there are no duplicates. Easy to collaborate across different teams and colleagues across the aisle.
Flexible Requirements Hierarchy Management: AZDO makes it easy to track items such as features or epics as a flat list, or as a hierarchy in which you can track the parent-child relationship.
Fast Data Entry: AZDO was designed to facilitate quick data entry to capture work items quickly, while still enabling detailed capture of acceptance criteria and item properties.
Excel Integration: AZDO stands out for its integration with MS Excel, which enables quick updates for bulk items.
There are a couple of areas where IBM Rational DOORS is quite strong. First, it is part of the IBM CLM solution so the artifacts developed in this module can be easily available for other functions like development and QA. They can link with their stories and test cases and team leads and managers can use traceability matrix to find out where there are gaps in coverage.
Comprehensive configuration management functionality (concept of multiple streams and global configuration) is available, which can be helpful if you need to implement configuration management scenarios for your product or project. For example, a certain version of a requirement can be linked with one story and another version of same requirement can be linked with another story. This is the unique feature which other current tools in the market don't provide.
It's highly customizable so you can configure the project areas based on your need. You can have your own requirement types, and you can define templates to speed up the process. Comprehensive review functionality is there as well.
Need to make the changes so that it doesn't occupy most of the CPU utilization and memory
Execution of Bulky SQl Queries leads to either the SQl being out of exception or the VS being unresponsive
Integration with Microsoft products is easy, but with non-Microsoft products it is more difficult, and you have to make a lot of configuration changes to integrate
With every upgrade of the Visual Studio, like from VS 2010 to VS 2013 , we need to upgrade our hardware/machine, as the VS hardware requirement also increases
If code is getting compiled in one visual studio, like in VS 2010, that the same code could possibly give an error when compiled in VS 2013, due to certain changes in keyword, data format, etc., with the VS upgrade
Too complex for projects or businesses that don't really need the detail. It is basically overkill.
If you are new to IBM Rational tools, it may be a medium learning curve. You'd also need lots of training from your people, since, as usual, this tool shouldn't be managed alone.
It may seem old fashion compared to Jira and the current control tools used in IT industry.
I don't think our organization will stray from using VSTS/TFS as we are now looking to upgrade to the 2012 version. Since our business is software development and we want to meet the requirements of CMMI to deliver consistent and high quality software, this SDLC management tool is here to stay. In addition, our company uses a lot of Microsoft products, such as Office 365, Asp.net, etc, and since VSTS/TFS has proved itself invaluable to our own processes and is within the Microsoft family of products, we will continue to use VSTS/TFS for a long, long time.
One of the downsides for us was the capabilities of the native build tools were lacking. The project management and work item tracking capabilities are great and I would recommend the tool to anyone. There is a definite learning curve with RTC as a source control system, and the streams are a concept unique to the product
Azure DevOps is a powerful, complex cloud application. As such there are a number of things it does great and something where there is room for improvement. One of those areas would be in usability. In my opinion it relies too much on search. There is no easy way to view all projects or to group them in a logical way. You need to search for everything.
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.
When we've had issues, both Microsoft support and the user community have been very responsive. DevOps has an active developer community and frankly, you can find most of your questions already asked and answered there. Microsoft also does a better job than most software vendors I've worked with creating detailed and frequently updated documentation.
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.
Jira is fantastic for project management and customer facing portal. It is not good for pure development (no integration with Git, pipeline management, automated testing features). If DevOps were to integrate and adopt the project features of Jira as well as the customer facing interfaces, I feel it would be a complete project management system.
The established experience contained in most IBM Rational DOORS installations is only compensated by the high flexibility of Atlassian JIRA. The markets state that Jira is less expensive in the setup. There are many manufacturers that support IBM Rational DOORS to have the big tiers as their customers. Jira has problems in that growth. Jira has more features compared to IBM Rational DOORS. For example in cloud support, IBM Rational DOORS relies on improved external services while Jira abstracts in the most modern way. Jira experts have a different professional background compared to that of IBM Rational DOORS. They are indeed from different engineering generations. There is little interchange in personal and ideas.
RTC helps automate incident management workflow which improves our work efficiency. With the integration with Geneos and GSD, we can one click create RTC incident tickets from Geneos with most of the information copied from Geneos automatically and then link the details to GSD for privilege account management if needed.
RTC provides a holistic view on ad hoc production activities. We use RTC for production management. Whoever needs to get access to production due to non-planned activities (planned change is managed in GSD) has to raise an incident ticket or service request ticket in RTC so as to get production privilege accounts.
RTC is also being used to review and approve the usage of privilege account which help us to meet audit requirements. For example, if a user made some database change using privilege account under incident number xxx, an entry will be added in RTC and sent to account owner or production support manager to review and approve.
