Jama Connect (Private Offer Only)

What do you like best about the product?

Jama Connect simplifies requirements engineering by providing a structured environment for managing requirements, reviews, and live traceability in one place. It helps teams collaborate more efficiently and improving visibility across the development lifecycle.

What do you dislike about the product?

While Jama Connect is excellent for requirements management and traceability, its SysML capabilities are more focused on supporting requirements-driven engineering workflows rather than serving as a full MBSE modeling environment. For teams looking for advanced system modeling capabilities, integration with dedicated MBSE tools may be needed.

What problems is the product solving and how is that benefiting you?

Jama Connect helps solve the challenges of managing complex requirements, maintaining traceability, and improving collaboration across cross-functional teams. It provides better visibility into product development processes and helps teams deliver higher-quality products with greater confidence.

What do you like best about the product?

Jama Connect is essentially a full-service, full-featured requirements management and traceability platform. It’s easy to use overall, and what I like most is its native review workflow and built-in traceability capabilities. The user interface is user friendly - except the recent change in the search for new project. Where you can only type a couple characters before the search starts. The performance is also very good. It still takes while to create a baseline - sometimes it takes long enough that I create request a second baseline before the pop-up shows. The only other performance issue is in the review activity log. It takes a very long time to pull that up. We currently use TaskTop for most our integrations. We will start using JCI in 1 month and I'm hoping use it for Jira and ReqIf integrations. The support team is amazing. They are highly available and informative is all aspects of needing assistance for myself as org admin, and for team members when they have questions I cannot answer. As for AI, the test case intelligence is very good. The feedback from the team is that it is helpful even in the situations where the requirement is complex or not written well. The JCA has been clumsy. However, an update has been made that, I hope solves that problem. I have not been able to look at that yet where the refinement is posted in the current requirement. I'll make a quick comment about the pricing - but my head doesn't really think in macroeconomics. I firmly believe the ROI of the tool is high- but I'm not good at placing monetary value on that.

What do you dislike about the product?

The only downside is that it is difficult to get the team up and running on AI capabilities. I mentioned in the last post that the JCA requirements advisor has been clumsy, and I think that interface can still use some 'ease of look' look-see. Again, the refinement update in 9.38 should solve some of the issues with it. The MCP is also not being picked up greatly by the team at RA. This is due (partly) to the copilot studio issue, that I think is just about to be released. But management feels that we are slow to see AI and MCP value (with the exception of test case intelligence) .

Baselines are an important part of archiving old work and releases. However the interface is very difficult. A quick fix would be so pin folders at the top of the baseline area. The biggest problem is that is a difficult area to keep clean due to the number of reviews and work complete in the project. And the people that can manage it are WAY TOO LIMITED. Everyone that creates a review or baseline should be able put it in a meaningful place in the structure in a baseline area. But since only admins can create folders or move content into them people just have to leave the baselines where they are created by the tool. NOT GOOD. This makes it a big effort to clean up for release and audit. This is one of the places where doing work later makes more work. It is a 'link while you think' -type of work and the baselines should be managed at the point of creation.

Another big problem that can be solved by Jama is the review information availability. We have a large enterprise problem where reviews are closed automatically (this is an equal problem with training and ease of use. But when we say it is a training problem, it is also an ease of use problem) Anyway, when the review is closed, the program manager does not have easy availability of the approval status of the review and the approvers. There are a couple reports, but we need a more native way to be able to access this information. This content should be better accessible by API, and better yet to be accessible by filters.

Another place where there could be improvement is the dashboards. We push to use the tool natively, so creating reports, though often works, isn not ideal. We need better complex dashboard capabilities.... with the ability to have 2 custom fields as variables - such as status per phase example.

What problems is the product solving and how is that benefiting you?

It solves our compliance needs by having the native review and traceability. These are the two biggest deliverables (other than requirements, of course) of 62443 for user. We have been slow to pick up live traceability - mostly because of the structural changes we need to make in the project to get away from a large all-encompassing relationship model to a multiples for focused relationship models.

What do you like best about the product?

I have found the user interface to be very clear and visual, compared to alternatives that I have used in the past. This helps when using Jama, and in particular when using Jama to explain concepts to colleagues who are non-experts (e.g the Traceability Information Model).

What do you dislike about the product?

It is not always clear how to set the Items up (e.g. fields and relationships) in the Admin tab, and online resources don't always specify when different options should be used. For example, why certain fields can or cannot be viewed in a Pie Chart dashboard. This led to me having to examine a Template Project and infer how to reproduce things via trial and error.

What problems is the product solving and how is that benefiting you?

Linking various different pieces of information together (e.g. company needs/requirements to design information) in a clear hierarchical manner, allowing us to work systematically to identify gaps.

What do you like best about the product?

Ease of setup and use. Traceability, Customer Access, No client install, Connection to other tools, and better in all ways over all other tools especially DOORs. Can be used on-prem or off-prem for unclassified and classified domains.

What do you dislike about the product?

Pricing model for Jama Connect Interchange tool follows other tools being charged per license vs per connection needs. If you have 50 licenses but only need 3 projects connecting to Jira we should not pay for 95% of 50 licensees not connecting to Jira.

What problems is the product solving and how is that benefiting you?

Time & money savings in touch labor in text-based requirements management with higher efficiency and quality of requirements generation and management.

What do you like best about the product?

What I like best about Jama Connect is its Live Traceability™ and ability to seamlessly bridge teams across software, hardware, and testing. It transforms requirements management from static spreadsheets into a real-time, interactive ecosystem. The upstream and downstream traceability makes change impact analysis effortless, which saves significant time during development and regulatory audits. Additionally, features like built-in decision tracking, real-time reviews, and seamless integrations with Jira and other ALM/PLM tools keep stakeholders aligned without communication bottlenecks.

What do you dislike about the product?

While Jama Connect is powerful, there is a noticeable learning curve for non-technical stakeholders or new users due to its deep configuration options and complex UI navigation. Additionally, configuring custom reports and exports can feel somewhat rigid without dedicated admin expertise, and performance can occasionally slow down when working with extremely large projects or complex trace matrices.

What problems is the product solving and how is that benefiting you?

Jama Connect solves the issue of fragmented requirements management across siloed tools, spreadsheets, and long email chains. Before Jama, tracking upstream system requirements down to hardware, software, and validation tests meant constant manual maintenance and high audit risk.

How it benefits us:
Saves Time: Real-time collaboration and automated review cycles drastically cut down approval times.

Reduces Risk & Rework: Full end-to-end traceability ensures we catch missing coverage or unlinked requirements early in the lifecycle.

Simplifies Audits: Generating compliance matrices and proof of verification for regulatory bodies takes minutes instead of weeks.