Jama Connect

Jama Connect is a solid framework for systems engineering that can integrate many design processes into a single tool. At a fundamental level, it is a great tool for handling requirements management and traceability but offers a variety of other features such as risk management and verification and validation. For someone who works in the medical device industry, the tool also complies with CFR requirements for electronic approvals and can be validated for such use.

Jama [Connect] seems like it would be a better product to use in a larger business setting where there are multiple offices or even multiple locations. We have a single location and we don't feel like it's the best for what we need to use for project collaboration. It seems too "large scale".

I am mainly in the Sales department, so using something like Jama Connect is probably not the best software suited for what I am trying to accomplish. If we were doing more things related to projects, I feel that we would be able to use Jama Connect to its full potential.

It's best suited for large distributed teams [that] are moving to an agile process. It enables large and complex system requirements management easier and efficient. Very much suited for SAFE - scaled agile framework implementation.

Nothing is perfect, but Jama has done a good job of implementing features that are representative of current methodologies. It's easy to get started and not too complex, but it could always be better. I think making use cases available to understand ways to improve our use would be good. Amazon does this with some AWS things where it has use cases of clients who have used a service/product and it can help teams/companies to implement new features, plus do things they may not have thought of before. Basically just examples but with some good details.

Jama Connect is well suited for an organization where it's required to include everything (required for a project / product) in one tool, i.e, from design specification till Test case reviews and defects as well. We can map the Design specifications with requirements (System / Software) and then with Test cases and we can track different changes done using Version history. Also we can link Test executions with test cases and also can keep track of different Reviews (Requirement/Test cases) and finally can link the defects logged in Jira with Jama as well.
If the organization is small / if the product /project is small & can be tracked easily, then Jama is not the better tool. Also, if we would like to automate any process /flow in Jama, then its bit difficult to develop the scripts and get the complete support for the same.

Good to manage product requirement for software and hardware and good to manage design and process FMEAs.
Not suitable to manage cases like issues experienced in project development for which we use other tools like Jira.

The fact that Jama Connect is a web-based application is very useful, especially in this new way of working remotely. It is well suited for large projects that are normally hard to manage without speciality tools. The user interface is very intuitive.

Jama is being used as a test management tool in my company. Am using Jama since 3+ years, and i can tell you that this was one of the best Test management tools I've ever used. Everything is so easy to understand and the interface is user friendly. Easy to use and can learn this tool fastly. I use this for Test plan, Test cases authoring, Test execution and results review along with the close out documentation.

I definitely recommend other organisations to use this tool.

Jama Connect is great at what it does, and so far, I have no real complaints about the ways that it has forced our teams to collaborate through the design inputs process and readdress good documentation practices.

Provides requirement traceability and also versioning, friendly UI.

What an amazing product! We were able to centralize our requirements process around Jama item workflows, Jama reviews, and the baselining locking I created (see one of my cons). I love how friendly it is to navigate. The dashboards are super neat and I look forward to seeing even more improvement on the dashboards.

It is a good way of providing a full framework for requirements management which is customizable; however, interoperability functions are not its forte. Support for ReqIF or other formats is not provided out-of-the-box, and would be very welcome. Also, integration with Jira requires a third-party product, but it is an integration that might be worth keeping in-house.

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.

Design control development of medical devices, especially for startup companies that can't invest the time and resources to make a fully custom solution. Jama works well "out of the box".

Jama is well suited for any level of requirement management. It's particularly helpful when you have several layers of requirements and several subsystems that interact. For very simple projects, however, with a limited number of requirements, Jama would still be beneficial, albeit less than the more complex projects.

We really like Jama Reviews for teams and Baselines for requirements. Traceability is well-structured although it has no flexibility with the relationships between types. It is very easy to drag and drop to rearrange the product requirements. I don't like the export capability or reporting. There is a lot of work to do to get the metrics we need from Jama Connect in Excel.

Jama Connect is well suited as an internal product management tool. The review center is great to review requirements electronically instead of sitting in a meeting to review them. Version control creates a great audit trail. The data exports to MS Office products have format issues. Time is wasted on document format revisions to send over to customers.

For requirements management, JAMA is very effective. They've nailed that. Once you start moving into other areas, it starts dropping off in functionality. JAMA seems to have taken a more rigid approach to these other areas (test management, design reviews, traceability, risk management). If only they could design these other areas to be as wonderfully flexible as the core requirements management functionality.

This tool is perfect to manage System of Systems until product level projects for TM, RM point of view. TM is also very easy to use and highly configurable to take into account most of our needs. Moreover through the RestAPI it bring lots of capabilities to interface with automated test tools. The ability of Jama Connect to manage libraries is also very appreciated to help the projects to focus mostly on the dedicated new requirements concerning their context, saving and securing time on what is reusable and already approved by experts. Review center and Baseline management are also great features provided by Jama Connect to secure the collaboration between teams and the configuration management.

Given our current process, Jama Connect presents some clear improvements. Obviously, it's ability to scale to large programs will be key. At the same time, having a centralized repository for documents, comments, etc., will allow for a rich integration of products and the ability to quickly perform an impact analysis. Most importantly, Jama Connect will need to pull from other tools that are currently in use to integrate itself into the process.

Jama is good for most applications. It is highly configurable which allows for a lot of freedom but relies on the organization to outline their desired process and definition of completion. As a power user, Jama has much of the functionality that we need but is missing a lot of the UX elements that encourage users, particularly new users or users who do not use Jama often, to engage with the tool. Its existing integration platforms are also subpar. Generally speaking, I would encourage other orgs to use Jama but would give them some details as to what challenges or limitations to expect.

Jama Connect is well suited if you talk about working together across the globe because this platform provides user connectivity with the project to not one but many colleagues at the same time. It is very important for any Project or Process to be circulated to each and every member involved in it so that there is no confusion about any area or topic and Jama plays crucial role in that. We just need to put all the information once on the portal and every related member can have access to that at same time. Any changes, chats, activity is circulated to everyone.

In the case of Requirement Management and Test Plans, Jama Connect is well suited. But in the case of tracking the progress of each requirement, task, or defect, JIRA is better than Jama. Workflows and other features of JIRA are better when compared to Jama. Also, Jama's backup strategy and support are not that as good as JIRA's. That's why I would not recommend Jama if you want more from the application.

Support teams fail to push the current defects to development teams to fix it. Jama doesn't provide 24/7 support, but it creates a lot of dependency. SOAP API calls and REST APIs are also not available for some of the automation which creates problems and adds extra cost to manage the resources doing those manually.

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.

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.

Jama is well suited for capturing requirements across the board for internal and external review. It is great for projects with multiple teams working together and going back and forth with clients for reviews. Easy to toggle between internal and external notes.