Confluence is a collaboration and content sharing platform used primarily by customers who are already using Atlassian's Jira project tracking product. The product appeals particularly to IT users.
$0
Free for 10 Users
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 Confluence
IBM Engineering Lifecycle Management
Editions & Modules
Free
$0
Free for 10 Users
Standard
$6.40
per month per user
Premium
$12.30
per month per user
Data Center
220,000.00
40,001+ Users - Annually
Enterprise
Contact Sales
No answers on this topic
Offerings
Pricing Offerings
Confluence
IBM Engineering Lifecycle Management
Free Trial
Yes
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
Prices shown here reflect prices for deployments with 100 users or less. The prices decrease wien the user base surpasses 100.
—
More Pricing Information
Community Pulse
Atlassian Confluence
IBM Engineering Lifecycle Management
Considered Both Products
Confluence
Verified User
Anonymous
Chose Confluence
Atlassian Confluence has a more comprehensive and flexible set of capabilities that stand out and made the decision upfront more straightforward for our team. The tools we evaluated have knowledge management, task management and collaboration capabilities, however Atlassian …
Atlassian Confluence is way popular for a larger team and makes collaboration way easier. The community is strong and you get easier resolution against any request. It's integration with other Atlassian products like JIRA is an icing on the cake.
In my experience, Atlassian Confluence is at the top of these tools. I've had first hand experience with other tools and they are not at par with Atlassian Confluence. The versatility of the tool is very well recognized and utilized. Being a new user is not a probably as all …
Atlassian Confluence is a super handy hub for sharing ideas and keeping all your docs in one place. While Jira Service Management is more about handling tickets and support issues, Atlassian Confluence really makes teamwork easy. I feel Atlassian Confluence is user-friendly, …
We choose Atlassian Confluence because it is the reference for managing a SAAS wiki service. And having such a solution in our company to manage the knowledge and especially the knowledge transfer is crucial.
Confluence has a more robust set of capabilities compared to Dovetail and Trello and also was already approved by our legal and compliance teams, so it tends to keep its stickiness due to that. It's also widely known in the market as a knowledge management tool. I would say it …
Overall, Atlassian Confluence is a user-friendly tool and offers such a vast array of capabilities for project and knowledge management purposes and beyond. Other tools listed above have much more limited capabilities, although they are great tools for very specific needs and …
Confluence, since it is part of the overall infrastructure of Atlassian, makes it immensely powerful internally, to build an internal knowledgebase, and is far ahead of its counterparts in Zendesk and Hubspot, which is more centered towards their customers. Confluence is just …
Sharepoint in out organisation was mostly used for collaborating on documents, which to some degree has been moved to Confluence, where the Confluence pages have replaced the specific documents.
Being a company which uses other Atlassian tools, Atlassian Confluence was a great fit; the natural and automatic linking of assets from other platforms made following paper trails seamless. Though the editing options aren't as advanced as some other options out there, it does …
We find Atlassian better for its ease of use, real time editing, integration with Jira for bug tracking, stores our security compliance documents in structured way, it is feature rich and have lots of capabilities.
In the past, I have used MediaWiki hosted locally as well as Microsoft Team Foundation Server. Wiki was simply a nightmare so all the money saved from paying for Atlassian subscriptions was lost in time while trying to use Wiki and format something properly. I haven't used …
Atlassian Confluence is better suited for documenting and acting as a repository for information than the more immediate what is currently being worked on things that are better suited for in Jira. In my opinion, Atlassian Confluence certainly has it's short comings but it is …
We still use Atlassian Confluence only for its integration with Jira and Bitbucket. For everything else, we moved away from it and are using more modern solutions.
We chose Atlassian Confluence over SharePoint because it's much more user-friendly and intuitive. Atlassian Confluence makes collaboration and knowledge sharing easier with its simpler interface and better search. While SharePoint can be powerful, it often feels clunky and …
The alternatives tested are based only on the whiteboarding functionality added by Confluence Whiteboard, and not the core Confluence functionality (documentation).
Again, Atlassian Confluence is efficient when paired with Jira and can do most of what a company needs it to do. But, I thi Spekit is better for "just-in-time" learning, Sharepoint is better for file hosting and organization, Asana is much better for project/task management, …
We were inclined to use Atlassian Confluence for its easy collaboration with Jira which is used for tracking project development tasks and issues. Using Atlassian Confluence, content creation became easy and even applying access control to the created content was possible. It …
We used to use a Wiki site, but that was locally hosted, and when the server was powered off, you could not access it. Moving to Confluence in the cloud is much easier. Also, the interface is much easier to use and expand.
Projektspezialist bei Steffen Jäschke EinzUnt Physik, Berechnungen
Chose IBM Engineering Lifecycle Management
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 …
I would choose IBM Rational DOORS over any other requirements management tool out there. Polarion tries to do too many things and is great for some things but as far as requirements management IBM Rational DOORS is the best tool on the market.
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 …
DOORS is not a suite nor an integrated tool like HP ALM or Rally. It only does one thing and cannot hold defects or accommodate sprint planning. It is older, takes longer to connect and load, and has an inconvenient timeout. It does do a basic job and can be customized to show …
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 …
To me, DOORS is like a super version of Excel and Word combined with a relational database. I have not used too many database softwares before, but DOORS does a very specific job well enough. It is so powerful that some of the tools just go unused. Some parts of the software …
Requisite Pro (and Rational Requirements Composer, it's successor) is more simple and focused on requirements. Is like a part of DOORS and can be suitable to smaller projects. IT people on the other hand prefer agile tools like Jira. Of course if the project is big enough, …
It's well integrated with IBM products so it provides better coverage across the lifecycle with first class integration. Other producst are stand alone with limited integration with ALM tools.
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.
It is easy for the organization to identify what kind of problems there are in the project and how many change requests have been resolved and how many are pending. Thereby the employer can pro-actively arrange the meetings and address the issues to the team members.
This product had many of the same features, was easier to use, which would result in less training, and had a lower price tag. Logic and reason do not always figure prominently in a decision. Sometimes there are intangible characteristics that alter the flow. In my observation, …
Atlassian Confluence is a great tool for housing important information and resources across the organization, as it's very easy to search and find content across different teams and departments. The search function is mostly very accurate and the additional tagging with keywords also helps in the search experience. It's also good at tagging other team members, which triggers an automated email to them. Atlassian Confluence also has an extensive template library for all kinds of purposes like project management, etc., which saves time overall.
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.
Its integration with Jira for tracking development and the bugs and work linked to detailed Confluence documentation.
We use it extensively for writing Software Product Requirement Documents, feature specs, architecture designs, and retrospectives.
Our company follows compliance very seriously, so it helps in streamlining all documentation for ISO27001/27017 compliance and security-related information.
Its integration with various tools allows us to create flow diagrams which are often required to make client and customer understand the overall flow of interactions across various modules of the design architecture
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.
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 am confident that Atlassian can come with additional and innovative macros and functions to add value to Confluence. In 6 months, Atlassian transformed a good collaborative tools into a more comprehensive system that can help manage projects and processes, as well as "talk" with other Atlassian products like Jira. We are in fact learning more about Jira to evaluate a possible fit to complement our tool box.
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
It's very intuitive for most things, making it easy to jump in and start creating pages and collaborating. This makes it ideal for onboarding new members to the team. There are a few areas that could be a little smoother, but overall it's a great experience.
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.
We never worked against the tide while using Confluence. Everything loads considerably fast, even media components like videos (hosted on the platform or embed external videos from Youtube, for example). We are not using heavy media components a lot, but in the rare occasion we happen to use one we have no problems whatsoever.
This rating is specifically for Atlassian's self-help documentation on their website. Often times, it is not robust enough to cover a complex usage of one of their features. Frequently, you can find an answer on the web, but not from Atlassian. Instead, it is usually at a power user group elsewhere on the net.
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.
Atlassian Confluence is a super handy hub for sharing ideas and keeping all your docs in one place. While Jira Service Management is more about handling tickets and support issues, Atlassian Confluence really makes teamwork easy. I feel Atlassian Confluence is user-friendly, integrates smoothly with other Atlassian tools, and helps everyone stay in sync. It's great for brainstorming, and project planning as well. Overall, it is a great way to boost collaboration and ensure all team members are on the same page.
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.
Merging instances has saved search time - We used to have several instances of Atlassian Confluence, which means they're separate and so can't communicate with each other. We've since merged into one instance and now with the help of the search feature can find the documents you're looking for in seconds rather than several minutes.
Cross linking product assets streamlines following paper trails - Being able to click on a BitBucket link from a Confluence page which then links to a JIRA ticket means you can follow paper trails really easily; seconds rather than several minutes.
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.