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
Polarion ALM
Score 9.3 out of 10
N/A
Polarion ALM is an application requirement management software platform now owned and supported by Siemens since the 2015 acquisition. It is available on the cloud (Polarion X) and on-premise. Polarion connect teams and projects to improve application development processes with
a single, unified solution for requirements, coding, testing and release.
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).
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.
Excel is the low-cost/low-feature requirements …
Jama is an excellent tool for requirements management, development, and traceability throughout the development lifecycle. Jama aids in peer reviews of generated artifacts with time-boxed review cycles. Jama provides a robust ecosystem which is highly tailorable to the demands of the particular organization in which it is used
Polarion ALM shines where it is intended to be used: Application Lifecycle Management. It fits well with agile development concepts, but the extensive customization abilities allow it to adapt to other concepts, too. It is suitable as an all-in-one solution, which is capable of giving transparency over all related areas, be it Requirement Management, Test Management, Release Management, Defect Management, etc., to the involved stakeholders.
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.
Polarion ALM provides a centralized repository for capturing and managing requirements. Teams can define, organize, and link requirements to other artifacts like test cases and development tasks.
Test Management:
Polarion ALM facilitates end-to-end test management. Teams can create detailed test cases, manage test execution, and track test results.
Traceability and Impact Analysis:
Polarion ALM ensures traceability across all phases of the development lifecycle. Users can establish links between requirements, test cases, development tasks, and other artifacts. This traceability helps in impact analysis, allowing teams to understand how changes in one area may affect other parts of the project.
Customization and Adaptability:
Polarion ALM is highly customizable to fit the unique needs of different organizations and industries. Users can create custom workflows, define custom fields, and adapt the tool to their specific development processes.
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.
More robust engine as far as the actual took is concerned. There are navigation components in trace to reporting which we feel can be improved especially when dealing with cross global accessing of the tool. It slows us down a bit so it's backend driven optimization as well as some front end "clunkiness" that can be improved.
Improve some filtering capabilities especially in creating custom reports and generally all around the ALM components of the tool.
As of the version we have, the ability to enhance replationship types in traceability is limited.
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
There is too much at stake to go into a new system. But with everything else being promised as far as newer more innovative products, the justification to not renew is a huge risk so that is not a concern
Jama is mostly designed for requirement gathering, but that can be possible using JIRA if we add only approval type of plugin for special requirement types. Jama's performance and features do not improve on a periodic basis i.e. with each release. Even bug fixes take a lot of time and they don't care about customer impact.
Jama is available most of the time if it is used within the application's boundary. Jama has very good availability if we use very high hardware servers. Sometimes we face issues if there are batch operations running.
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.
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.
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.
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 additional selling points. Availablity of support in our local language was much appreciated as well.
Polarion ALM has the best usability, extensibility and reactiv product management. The support is also very good compared to other companies. Or in other words it is closer to the customer. Codebeamer is for sure also a good ALM tool with a great feature set, but existing customers are often neglected. We will see, what PTC as the new owner of codebeamer will change at this point.
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.
