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
Jama Connect
Score 9.4 out of 10
Enterprise companies (1,001+ employees)
Jama Connect® is a Requirements Management software and Requirements Traceability solution. Jama Software enables teams to manage product requirements and enable Live Traceability™ across the development process, in order to reduce cycle times and improve product quality.
N/A
Pricing
Atlassian Confluence
Jama Connect
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
Jama Connect
Free Trial
Yes
Yes
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
Jama Connect
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.
Microsoft Excel provides only barebone capability when it comes to requirements development, since it is not primarily designed for that purpose. It is therefore not a serious contender to the capabilities of Jama Connect
in terms of features they were similar. The difference was due on the architecture of Jama Connect which apperas more simple and effcient. Polarion was relying to an SVN database.
Jama Connect was the perfect balance between cost, usability and scalability that our company desired. Helix was definitely cheaper but didn't offer the usability or scalability perks. Codebeamer missed the mark on cost and was designed more for a software centric requirement …
Jama Connect is more straightforward than these systems but not quite as versatile or comprehensive. I would choose those other systems if I were at a very large company working on very complex systems (which I am not).
I really liked Cradle as it seemed to be very full-featured. BUT, my liking for it was predicated on my being a daily user of the tool; it took me a while to get familiar with the tool. What was certainly true of Cradle in my experience was that it was VERY challenging to get …
Polarion did not have the outside sales support that Jama Connect has. Polarion seems better suited for an Agile development lifecycle rather than an evergreen repository of requirements, design features, and verifications.
The major sellingpoints of Jama were the review-system for internal and external reviewers and the inclusion of (Use Case) modelling tools, while keeping the core requirements-centric. Ability to synchronise with currently in use test-tooling and the low learning curve were …
JAMA can navigate between them, as far as it generates reports accessible through MS Project, Word, and Excel. Moreover, very likely it can be embedded into Confluence as well however, we have not yet implemented this feature.
From a technical point of view, DOORS is much more customizable than Jama Connect, and this is more useful when talking about SW related requirements; when talking about system related requirements, Jama Connect is well suited with respect to DOORS, in the sense that …
Jama brings requirements engineering to the 21st century and sets up the bar to measure other tools. DOORS and DNG never managed to make this jump and stayed in the past.
We originally looked at Connect (Contour) and Doors as we wanted to move away from Word documents. Contour was much easier to use and had a better collaboration environment. The was many years ago; I haven't done any comparison in the last 5+ years.
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.
Jama connect has the best UI compared to DOORS, Codebeamer, and PTC Integrity. It’s the clearest to use with the best usability. For example make traces between all requirements is as straightforward as clicking a button. The trace matrix view is highly configurable to get you to show anything you need. It has extensive filtering where every index in your requirement is indexed. Same with their export features, you can use default templates or create custom templates to export to PDF for all your regulatory needs like submitting documentation to FDA. This has helped us a ton without requiring much edits and letting us create up to date reviewed documents.
Speaking of review system, it’s well organized and you can set required approved and optional reviewers. Track your redlines in the tool and also view and resolve comments.
The one issue I’ve experienced is that with a large system the web app can take some time to load everything.
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
Focus in the content without loosing the track of the evolution of the items by maintaining the exchange of information between the users inside the Tool.
The possibilities to integrate this tool within our IT-landcape and with our other engineering tools is for us a leverage to success.
The 'filtering' capabilities in Jama are not as good as they could be. In particular, the ability to "nest" filters is quite limited. I have certain seen much better capabilities in other tools. ('Cradle' is an example of a tool with excellent "nested filters" capabilities.)
From an administrative point of view, the 'License' admin view is pretty disappointing. The particular thing that I'd like to be able to find out from it is the peak number of 'Float Creator' licenses in concurrent use on each day. If there's a way to get to that information, I haven't found it yet.
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.
Jama is really easy to use and operate compared to other tools. This allows a process owner to get easier buy-in from the organization to see value early. My experience with this tool was very positive and we were able to see value early in its introduction
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 requirements and baseline parts are easy to use. The review centre is very useable and understandable, once you understand/set up the moderation. (This last part could use some refinement.) Integration/connectability (the Connect part of Jama) is quite possible, but the useability could use some love as well.
It has always been available, except for preventative maintenance which is announced beforehand. Nonetheless, we experienced one day shortage over a miscommunication about payment.
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.
With performance compared to JIRA, I do recommend Jama in this case. Jama provides very good performance, it loads immediately for any of the items and searches any item immediately. Performance is really good in all of the operations including creating stories, epics, item types or other support operations or report generation.
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.
They typically answer within minutes of posting a ticket, and then you have a clear expectation of what the issue is, how to diagnose it, how long will it take to get resolved, and in which version a given problem is resolved, or if there is a patch for hosted services. They have a number of support people, and all of them are top-notch.
Helpful and exhaustive and tailorable for our needs. Instructor was well versed and engaged. Material was a good reference and was up to date with tool. Overall, in person training was valuable for tool introduction. Trainer was an active user of the tool and worked closely with other clients. So, very knowledgeable.
Easy to reference and understand. Updated routinely to include new topics. Online training evolves to include more advanced topics and how to guides. Online training includes videos and reference guides that make it easy to perform more complex tasks. Online training is free and can be accessed from any computer.
Jama 2015.5 implementation is very smooth and no need for much manual work. Jama 8 has many challenges and we can not install it as smoothly as Jama 2015.5. Initially, Jama didn't provide the Jama 8's installer files or zip files and they were just providing docker files to everyone (which was really strange). It is the worst that they don't provide all the files at a time. Why should they tell us where we should deploy, and why only a dockerfile? I am not very satisfied with Jama implementation.
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.
JCA is an extraordinary tool that is very simple to use and brings efficiency to the creation of requirements. It is particularly good at highlighting improvements to requirements which, when done properly and done up front in the engineering development process, will save significant time and prevent confusion downstream in the development process. It's difficult to quantify how much of a positive impact JCA would have on any individual project, but I would say it could easily save an organization more than its cost in terms of improving efficiencies and the traceability integrity throughout the entire portfolio of projects when applied correctly. This additional product from Jama is highly recommended.
There is no horizontal scalability available in Jama, we have only one choice to scale it vertically. But vertical scalable applications always have limitations to grow. In this case, Jama doesn't support horizontal scalability functions like multi-node architectures with a shared drive for the home directory.
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.
One experience that converted an engineer to using Jama Connect was an electronics engineer that was writing test plans. I showed them about how to write "unit" or very discrete tests and then showed them an automatic export to get the document. Thus the authoring of the document effort was taken away, they could focus on defining the test
Unfortunately I have very much struggled to embed systems engineering, requirements management and Jama Connect as part of the 'ways of working' outside the systems and electronics teams.
