What do you like best about the product?

1. Flexible Item Configuration and Customization
Jama Connect offers a highly flexible configuration environment that enables users to tailor item types, workflows, and attributes to their specific project or organizational needs. This adaptability ensures that teams across various industries can align the platform with internal processes, compliance requirements, and traceability standards. The system supports both simple and complex customizations, making it suitable for agile, waterfall, or hybrid methodologies.

Key Strengths:
- Custom item types and fields for modeling unique data structures.
- Configurable workflows and statuses for each item type.
- User role and permission settings that allow secure, role-based access.

2. Robust End-to-End Traceability
One of Jama Connect’s standout features is its robust traceability model. The platform supports linking between all key artifacts—from requirements and tests to risks and validations—enabling full visibility across the product lifecycle.

Benefits:
- Easy creation and visualization of trace relationships using the Trace View and Trace Matrix.
- Identification of gaps, risks, and dependencies early in the process.
- Enhanced support for compliance audits and impact analysis.


3. Review Center Functionality
The Review Center provides a streamlined and collaborative space for conducting formal and informal reviews. It enables stakeholders to efficiently comment on, approve, or reject items under review while maintaining a comprehensive audit trail.

Key Capabilities:
- Launch and manage structured review cycles.
- Monitor reviewer participation and feedback progress through visual statistics.
- Approve or request changes with clear version control and resolution tracking.

This review mechanism improves stakeholder engagement, reduces review time, and ensures that critical feedback is captured and acted upon efficiently.

What do you dislike about the product?

1. Limited Reuse of Multiple Item Types from Baselines and Filters

Jama Connect imposes restrictions on reusing multiple item types at once—either from baselines or filtered lists. While it is possible to reuse multiple items of the same type, there is no functionality that supports bulk reuse across different item types in a single operation.

Key Challenges:
- Users cannot select and reuse a combination of different item types (e.g., requirements, risks, and test cases) in one action.
- Bulk reuse is only supported when all selected items are of the same type.
- This limitation is particularly problematic when reusing sections of a project or product definition that span several types of artifacts.
- Filters also do not allow bulk reuse across item types, further complicating cross-project modularity.

2. Fragmented Item View Configuration
The process of configuring item views is unintuitive and lacks flexibility when working across different views or contexts.

Specific Drawbacks:
- New item creation does not prompt or guide users to configure the view layout.
- Users must manually remember and apply their preferred field layout each time.
- It is not possible to apply a consistent configuration across all views—requiring redundant setup for each view separately.

3. No Option to Copy Dashboards
Jama Connect does not currently support duplicating or copying dashboard configurations between users, teams, or projects.

Impact:
- Rebuilding dashboards from scratch for each new project wastes time.
- Reduces standardization of views and reporting across teams.
- Limits the scalability of workspace templates and best-practice reuse.

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

1. Aligning All Participants on a Single Page
Challenge: In complex projects with cross-functional teams and multiple stakeholders, ensuring that everyone is working from the same source of truth can be difficult.

How Jama Helps:
- Provides a centralized platform where all stakeholders—product managers, engineers, testers, and external partners—can collaborate in real time.
- Supports structured reviews and approvals, ensuring feedback is captured, aligned, and traceable.
- Role-based permissions ensure the right people see the right content at the right time.


2. Ensuring End-to-End Traceability
Challenge: Projects often suffer from a lack of visibility into how requirements evolve into design, test cases, and final deliverables—especially under regulatory or safety-critical contexts.

How Jama Helps:
- Offers complete traceability across all artifacts—from requirements and risks to test cases and defects.
- Enables impact analysis to assess the ripple effects of changes.
- Supports compliance with industry standards through clear linkage and trace paths.


3. Measuring Progress of Product Development
Challenge: Teams need clear visibility into development progress to identify delays, dependencies, and areas of risk early.

How Jama Helps:
- Dashboards and reports provide real-time insights into project status, item completion, test coverage, and reviews.
- Enables metrics-driven decision-making based on up-to-date information.
- Visual indicators help stakeholders track review cycles, approval states, and trace gaps.


4. Consolidating All Information in One Place
Challenge: Fragmented tools and disconnected documents make it difficult to maintain consistency and control over project data.

How Jama Helps:
- Centralizes all product-related information—including requirements, decisions, comments, and documents—into one structured system.
- Reduces version control issues and eliminates information silos.
- Facilitates faster onboarding of new team members by having a single source of truth.

5. Receiving Fast Feedback from Clients
Challenge: Slow or unclear communication with clients can lead to rework, delays, and missed expectations.

How Jama Helps:
- Review Center allows clients and external stakeholders to review and comment on requirements in a structured and traceable way.
- Speeds up feedback cycles with clear visibility into review status and participation.
- Helps validate requirements early and often, reducing the risk of building the wrong product.

Recommendations to others considering the product:

Be careful with adding a new data field to the item. Too many data fields can slow down the process.

What do you like best about the product?

A tool for tracking requirements and online traceability that displays the upstream and downstream relationships from product requirements to technical specifications, to test cases, and to test runs.

What do you dislike about the product?

The user interface could be more streamlined. Sometimes creating relationships can become tedious. Some users have their account type changed without their knowledge. It changes from creator to collaborator, and they lose their ability to create or edit items.

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

Requirements tracking and traceability are very useful during reviews to show that for each requirement, there is at least one corresponding technical specification, test case, and test run.

Recommendations to others considering the product:

Take the time to learn the many shortcuts available.

What do you like best about the product?

Being a web tool is by far the most important aspect of the tool. That portability removes any need for update management and requirement server sync problems that are encountered with desktop applications in an enterprise environment.

What do you dislike about the product?

I really wish Jama implemented traceability rules. Currently, to enforce requirement traceability the way my organization would need to most, I'd have to implement many duplicate (but separate) object types. The most important basic rule I'd like to see implemented is when checking for link compliance that parent links can run against an OR operator instead of only an AND operator. In otherwords, to prevent "orphaned requirement," notice when both parents are not present to allow "at least one of the required parent objects must be present" message. This would be most important for traceability to test plans, where we'd like to use the same test plan object type to verify a variety of objects.

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

I'm using the deployment of Jama in my organization to enforce good design thinking. Encouraging others to think about how requirements are derived and what constraints a project needs to execute an acceptable project.

What do you like best about the product?

It's user-friendly and easy to learn. Traceability and versioning saves us alot of time.

What do you dislike about the product?

It would be nice if there was a way to import storycards into Jama without it being time consuming and a a manual job.

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

Traceability, versioning, consistency, making requirements easy to locate, time savings, better collaboration.

What do you like best about the product?

The tool is an integrated solution for requirements, risk, and test management.

What do you dislike about the product?

Currently not fully compliant to 21 CFR Part 11.

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

Efficient creation and review of requirements; Easy tracing of requirements through test plans, test cases, and test results

Recommendations to others considering the product:

Jama Connect is a very flexible tool. Please don't underestimate the effort required to align it to your current requirements management workflow.

What do you like best about the product?

The review center, in my opinion, is the star of the Jama product. It promotes collaboration and its simple to use. Informally speaking, I think our end users enjoy the review center process the most. Since implementing Jama, we have seen an increase in customer participation in our internal projects.

Managing the sign-off and consensus on specific requirements was a challenge until we purchased Jama. Requirement management comes in a close second.

What do you dislike about the product?

The product can be overwhelming, even for someone who has used it for several years. Also, the legacy synchronization process was simple and straightforward. We since had to move to OPSHub, which was not as simple.

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

When we purchased Jama a few years ago we were trying to solve the following challenges:
1.) How do we deliver requirements to our customers in such a way that they stay informed?
2.) How can we maintain project requirements in a centralized location?
3.) How can we ensure the right people have agreed to requirements before transitioning to development?
4.) How can we consistently provide our programmers with the information needed to develop software.

Since we have implemented Jama we have realized the following benefits:
1.) Requirements are no longer gathered in a vacuum amongst business analysts.
2.) Increased customer participation in the requirements review process.
3.) Consistency in the requirements gathering, management, delivery process.

Recommendations to others considering the product:

I have used other requirement management products in the past, and by far, this is the best one overall.

What do you like best about the product?

Re-usability of components, sharing docs with external clients

What do you dislike about the product?

Some of the reporting output is not easy to render/read

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

Sharing business documents with clients, automating the sign-off process and maintaining history on reviews. The review process has been streamlined and is very efficient reducing overall timeline for sign-off.

What do you like best about the product?

Ease of use and low barrier to entry. Once configured, the tool is usable within a few hours for all staff, even without Systems Engineering experience. Most importantly, it doesn't slow down or get in the way of the engineering.

What do you dislike about the product?

Some useful new features have been slow to implement

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

Significantly reducing rework and time to market across multiple businesses who adopt Jama. Avoids errors in design process, helps link engineers to market needs and improves reuse.

Recommendations to others considering the product:

Consider getting some training and support for basic systems engineering and requirements management principles. While Jama is really easy to use, teaching all staff the basics of Systems Engineering (e.g. 2-3 days training) will really get the best outcome

What do you like best about the product?

It is a very well thought and engineered solution with some very good "out of the box" regulatory reports. JAMA Connect is very intuitive and ease to use by our teams.

Besides the tool solution, I also really appreciate the JAMA Software team that understand our core business and helps us along the way from a technical stand point.

Finally, the JAMA community web site as well as the regular webinars offered are extermely value-add additional resources.

What do you dislike about the product?

The limited dashboarding option for now is gap. Some alternative solutions exist but I will appreciate a comprehensive out-of-the-box set of dashboards to help our Dev teams and Leadership.

A connected Risk module with the Project module will laso be very beneficial.

A huge quick win will also be to provide conditional options to adjust the item's fields based on context. (example: if "x" in a check box than show those additional fields ...).

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

To provide a Digital DHF for our SaMD solutions.

Recommendations to others considering the product:

Release after release new features and improvement appears to make JAMA Connect even better, JAMA Software as a company knows what they are talking about and can help you expedite your digital transformation.

What do you like best about the product?

Traceability features
Test case execution traceability

What do you dislike about the product?

Some of the UI seems complex at first...

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

Saving resource and staff time in defining requirements and traceability regarding product systems engineering

Recommendations to others considering the product:

Plan your workflows early.
Learn all the features and benefits upfront.