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
Jira Software
Score 8.1 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.
We are using Confluence for software projects requirements. Even if it is not as dedicated to requirements as Jama is, software developers will choose Confluence over Jama if they already have JIRA for their Agile software development. The Confluence macros are a big plus over …
I have mostly worked with ALM and JIRA Software. they are good enough to gather the requirements but not much like Jama software. JIRA doesn't provide approval mechanism and ALM doesn't provide traceability and reuse or reviews functionalities so in all of them Jama is better …
I haven't used the other tools in some time, but I know I prefer Jama over Jira and MS Project. Again, this is skewed based on the fact that I haven't used the other 2 tools in years. Jama is used more by clients whom I work with so it seems to be more of a market leader than …
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.
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.
Verified User
Team Lead
Chose Jama Connect
Ease of access.
TBH, polarian looks so weird for me and am not a big fan of that tool. I even don't like it's UI
Alternatives to Jama for us is Google Sheets. I have spent significant amount of time getting the team away from sheets as a source of truth. The added features of Jama has helped the team transition to Jama for the source of truth for requirements.
We tried to do with Requirements management with Confluence and other Atlassian marketplace tools. The Jama traceability is still the overriding decider for staying with Jama. FYI, we paid for Jama/tasktop for several years without doing the integration - you would think that …
Jama does the requirements management piece better than anyone else, which is why we chose it. The cost was hard to swallow, given the limitations of the other areas of the product (test management, risk management). Products like Helix are better for testing, but are pretty …
I have used MS SharePoint and Confluence before and feel that as a requirement solution, Jama is more intuitive and easier to maintain requirements and have traceability. It is easier to maintain upstream and downstream relationships in Jama which I feel is a very good feature …
Jama suited our need for collaboration and communication plus a difficult stakeholder's approval roadblock. Jama provides a very easy to use interface and communication system that brought in the buy-in from all stakeholders based on the communication problems we needed to solve.
Jama provides cleaner workflows for entering requirements and a really efficient and robust workflow for approvals which other products didn’t have or were still maturing.
Each application comes with their advantages. Jira Software is one for the tools famous among our Post Market Surveillance and Engineering teams due to its simple application structure. Provide easy tracking and navigation through the tool which helps with monitoring more …
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
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.
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.
Jama Connect is not adding many extra features with their major releases. It showed launched new features, but those are not very useful for developers or creators working with Jama. From the performance side, Jama has been reduced it's performance in Jama 8 as compared to Jama 2015.5 from the functional perspective. The test suite must be provided by Jama to test the performance and function of things in our instance, but Jama doesn't provide it. Also, Jama requires a lot of manual intervention for adding users.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.