Jama Connect

What differentiates Jama Connect from other similar products?

The ease of use is one of the main items which stands out, and the ease of creating your business forms for use as well.

What is your favorite aspect of this product?

Since we shortly used the interface with other systems we are looking forward to establish a lot more connections to third party .

What do you dislike most about this product?

The administration module is fairly simple and I would like to see more information regarding the number of logins who logged in when did a user logged in the las time. Knowing what users are doing read, write update items.

What recommendations would you give to someone considering this product?

Know your system landscape in your company and what you would like to gather on information on a project. Make sure all departments (such is the case in our company Electrical, Mechanical, Project Managment, Procurement, Software development, Electro-Optical etc) can use the same form for all the Items you define.

What differentiates Jama Connect from other similar products?

The important difference is how it handles complexity and tools like Jira or Azure DevOps are excellent for managing tasks and workflows, but they are primarily built for execution speed. Jama Connect is built for getting the system right before and during execution, especially in environments where multiple teams, hardware/software integration, or regulatory requirements are involved. And it also stands out in how it handles reviews and collaboration.

What is your favorite aspect of this product?

Jama feels different. Because everything is inherently connected, when we change a requirement, we can immediately see what tests, risk, or downstream items might be affected. And it’s not flashy, and it’s definitely not the fastest tool to work in a day-to-day, but that clarity is powerful. It shifts our mindset from just pushing tickets forward to actually understanding the system as a whole.

What do you dislike most about this product?

There is a but of a learning curve. New team members don’t just pick it up in a day or two. We need to understand how items, relationships, baselines, and reviews all fit together. Until that clicks, it can feel unintuitive. And compared to something like Jira, where we can spin up a ticket and move on, Jama often makes us think through hierarchy, links, and traceability even for small changes.

What recommendations would you give to someone considering this product?

The thing i would recommend is to invest in onboarding and setup early. Jama isn’t something we just install and figure out along the way. The value comes from how well we model our requirements, workflows, and relationships from day one. And i would say that to be really honest about how complex our product actually is. Jama shines when we are dealing with systems where requirements, tests, and risks, are interconnected think regulated industries or large multi-team environments.