IBM Engineering Lifecycle Management vs. Jira Software

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
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
Jira Software
Score 8.0 out of 10
N/A
JIRA Software is an application lifecycle management solution for software development teams. It allows users to create, prioritize and track the progress of tasks across multiple team members, and offers a wide range of integrations. It is offered via the cloud and local servers.
$10
per month
Pricing
IBM Engineering Lifecycle ManagementJira Software
Editions & Modules
No answers on this topic
Standard
$7
Per User Per Month
Premium
$14
Per User Per Month
Free
Free
Enterprise
Contact Sales
Offerings
Pricing Offerings
IBM Engineering Lifecycle ManagementJira Software
Free Trial
NoYes
Free/Freemium Version
NoYes
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
IBM Engineering Lifecycle ManagementJira Software
Considered Both Products
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.
Chose IBM Engineering Lifecycle Management
An alternative which I have very briefly used is Atlassian's JIRA, which is very similar to IBM RTC, although has a modern UI, feels light-weight and is faster to respond and additionally has seamless integration with Bitbucket, which is a Git platform, and other Atlassian
Chose IBM Engineering Lifecycle Management
Although JIRA is getting popular in DevOps team, it does not work well with ITIL model as RTC does. RTC is still widely used for production management in our company.

CA Service Desk Manager (GSD) is integrated with TPAM which is being used for privilege account management in …
Chose IBM Engineering Lifecycle Management
My organization was already using it when I joined the team.
Chose IBM Engineering Lifecycle Management
I have worked on different agile project management tool like JIRA, Teamfoge and RTC. RTC is simple and has a nice UI.
Jira Software
Chose Jira Software
JIRA suits the project need as we do not need such a complex requirements management tool and cost is an important factor.
Chose Jira Software
JIRA is way better than the IBM Rational suite, in every way i can think of, right from the user experience and look and feel. For someone who spends a lot of time per day with these tools it makes a big difference to their overall productivity.
Top Pros
Top Cons
Best Alternatives
IBM Engineering Lifecycle ManagementJira Software
Small Businesses
Polarion ALM
Polarion ALM
Score 9.2 out of 10
Polarion ALM
Polarion ALM
Score 9.2 out of 10
Medium-sized Companies
Polarion ALM
Polarion ALM
Score 9.2 out of 10
Polarion ALM
Polarion ALM
Score 9.2 out of 10
Enterprises
Polarion ALM
Polarion ALM
Score 9.2 out of 10
Polarion ALM
Polarion ALM
Score 9.2 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
IBM Engineering Lifecycle ManagementJira Software
Likelihood to Recommend
8.8
(22 ratings)
8.7
(187 ratings)
Likelihood to Renew
8.0
(6 ratings)
9.0
(35 ratings)
Usability
2.1
(4 ratings)
7.0
(28 ratings)
Availability
-
(0 ratings)
5.3
(3 ratings)
Performance
-
(0 ratings)
8.0
(1 ratings)
Support Rating
5.0
(3 ratings)
8.8
(23 ratings)
Online Training
-
(0 ratings)
8.0
(1 ratings)
Implementation Rating
10.0
(1 ratings)
9.0
(1 ratings)
Ease of integration
-
(0 ratings)
7.7
(8 ratings)
User Testimonials
IBM Engineering Lifecycle ManagementJira Software
Likelihood to Recommend
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
Atlassian
The Jira software works well for managing scrum boards and allocating resources to a task. When your Epics and Issues are set up properly, it can give you a good idea of where your team stands and the trajectory of your project. It is not the ideal solution if you need to provide documentation and support to people outside of your product teams or organization. It would benefit from having a public documentation or repository feature.
Read full review
Pros
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
Atlassian
  • Running sprints and tracking progress of roadmap, epics, story, task and subtask
  • The user interface is great. It allows tables inside details, have common shortcuts and clean design.
  • Can create custom dashboards and can view data in multiple ways
  • Advanced access rights based on role
Read full review
Cons
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
Atlassian
  • Management of the software is very difficult at times, although has improved.
  • Ability to manage resources is really non-existent, there are some plugins but they are ALL buggy (I've tested them all).
  • Better integration with Trello, would love to see this happen. Right now it's very clumsy.
Read full review
Likelihood to Renew
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
Atlassian
This is because Jira Software generates a huge profit for an affordable price. Having a tool that makes team management transparent and effective is very valuable.
In addition, the renewal of Jira Software and all Atlassian tools is predictable and clear, as the prices are published on the Atlassian website and there is no pyramid of intermediaries.
Read full review
Usability
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
Atlassian
JIRA Software is a pretty complex tool. We have a project manager for JIRA who onboarded us, created our board, and taught us the basics. I think it would have been pretty overwhelming to learn without her. JIRA offers so much functionality that I'm not aware of -- I constantly need to Google or ask others about existing features. Also, although they are all under the Atlassian umbrella, I find it difficult to switch between JIRA Software and Confluence.
Read full review
Support Rating
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
Atlassian
Our JIRA support is handled internally by members of our Product Support team. It is not supported by a 3rd party. Our internal support will always sent out notifications for downtime which is usually done on the weekend unless it is required to fix a bug/issue that is affecting the entire company. Downtime is typically 3-4 hours and then once the maintenance is complete, another broadcast email is sent out informing the user community that the system is now available for use.
Read full review
Online Training
IBM
No answers on this topic
Atlassian
One of their strong points i stheir documentation. Almost all of the basic set up needed within JIRA is available online through atlassian and its easy to find and very precise. The more critical issues need to be addressed as well and hence the rating of 8 instead of a 9.
Read full review
Implementation Rating
IBM
No problems
Read full review
Atlassian
Take your time implementing Jira. Make sure you understand how you want to handle your projects and workflows. Investing more time in the implementation can pay off in a long run. It basically took us 5 days to define and implement correctly, but that meant smooth sailing later on.
Read full review
Alternatives Considered
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
Atlassian
Jira Software has more integrations and has more features than many of its competitors. While some of its competitors do have better UI/UX than Jira Software, they have improved this greatly over time. Atlassian also acquired Trello years ago, so that adds better user interfaces to the system. They do also offer a pretty in-depth library of how to customize the platform that others don't.
Read full review
Return on Investment
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
Atlassian
  • Jira has positively made our company's daily activities much better organized
  • With Jira we can track progress and follow up on tasks
  • Jira has great reporting tools which aggregate various data and give us a good overview of our teams capacity
Read full review
ScreenShots