Atlassian Jira is a project management tool, featuring an interactive timeline for mapping work items, dependencies, and releases, Scrum boards for agile teams, and out-of-the-box reports and dashboards.
$9
per month per user
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
Atlassian Jira
IBM Engineering Lifecycle Management
Editions & Modules
Standard
$9
per month per user
Premium
$17
per month per user
Enterprise
Contact Sales
per year
No answers on this topic
Offerings
Pricing Offerings
Atlassian Jira
IBM Engineering Lifecycle Management
Free Trial
Yes
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
Higher volume teams may qualify buyers for a discount.
—
More Pricing Information
Community Pulse
Atlassian Jira
IBM Engineering Lifecycle Management
Considered Both Products
Atlassian Jira
Verified User
Consultant
Chose Atlassian Jira
JIRA suits the project need as we do not need such a complex requirements management tool and cost is an important factor.
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.
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 …
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 …
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.
Jira facilitates software development, bug tracking, and sprints. It's ideal for structured workflows, issue management, and customer communication. However, more straightforward tools might be more efficient for highly creative, unstructured tasks or tiny, agile teams with quick visual overviews. Jira's complexity can be overkill for basic task lists.
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.
Integration of tools like Bitbucket, Github, etc., has made it easier to track the code changes, pull requests, and branches linked to the respective ticket.
The detailed tracking system in JIRA has helped the teams prioritize and understand the project tasks and issues.
JIRA's project tracking board helps you keep track of the project, its flow, and expectations in a structured format.
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.
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.
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.
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.
The interface is simple and easy to use if you have some experience with it. Configuration is also logical most of the time. However, less experienced users tend to find themselves lost in some tasks - usually complex project configuration- but sometimes simple things, such as seeing why a user can't move issues in a workflow. Jira configuration requires a good amount of experience - and even experienced users often resort to documentation. It's a tool that's easy to use if you know what you're doing and where to find the proper documentation, but novice users tend to find it challenging.
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.
Did not face any issues and whenever they plan maintanance they update all of us very well in advance also so in that view we are good with the product stability.
Performance is really good though it holds lot of data it loads quickly especially search operation also get the results very quickly as needed hence its good
I have not had a chance to contact JIRA's customer support. It does offer extensive documentation, although it often feels too technical for me. There is also a JIRA training app that lets you take little lessons and quizzes on different areas (e.g., JIRA basics, agile). I did find it a helpful way to teach myself.
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.
Had received training from our own internal user so it was good and also very easy to understand topics and many tasks in the UI are self explanatory and we can do by our own
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.
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.
monday.com cannot be integrated with CI/CD tools, whereas Atlassian Jira integrates with CI/CD tools seamlessly. Atlassian Jira has strong Agile and Scrum support. Coming to monday.com, it has basic agile functionality. But Atlassian Jira has a complex UI, and monday.com has an intuitive, drag-and-drop interface. Overall, Atlassian Jira provides features like Agile project management, DevOps integration, and customizable workflows.
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.
Atlassian Jira's robust workflow automation has boosted team efficiency, shortening delivery cycles and driving a positive ROI through improved project management.
Its advanced reporting and integration capabilities have enabled data-driven decisions, aligning operations with key business objectives.
However, the steep learning curve can delay adoption, potentially hindering short-term ROI.
