Jama Connect (Private Offer Only)
Jama Software (Private Offer Only)External reviews
199 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Jama connect review
What do you like best about the product?
Requirements management tool, cloud based
What do you dislike about the product?
Test centre not suited for medical devices
What problems is the product solving and how is that benefiting you?
Cloud based tool for clients
Easy to use web-based (SaaS) tool that offers acceptable Requirements & Test Management
What do you like best about the product?
1) Easy to use but still acceptable configurability (data model, item types/fields, item relationships, workflows, etc.)
2) Web-based/SaaS with frequent updates (bug fixes and new features)
3) Support for both Requirements & Test Management in the same tool (this means support for traceability analysis, etc.)
4) Jama Review Center (best tool we have found so far that includes a comprehensive review/approval process)
5) Overall good performance and high availability (no major downtimes over the past 2-3 years)
6) Acceptable integration/interoperability (REST API, export/import, etc.)
7) Collaborative (mentions, subscribe to items, etc.)
8) Excellent technical support!
2) Web-based/SaaS with frequent updates (bug fixes and new features)
3) Support for both Requirements & Test Management in the same tool (this means support for traceability analysis, etc.)
4) Jama Review Center (best tool we have found so far that includes a comprehensive review/approval process)
5) Overall good performance and high availability (no major downtimes over the past 2-3 years)
6) Acceptable integration/interoperability (REST API, export/import, etc.)
7) Collaborative (mentions, subscribe to items, etc.)
8) Excellent technical support!
What do you dislike about the product?
1) Test Management (Jama Test Center) is primarily for manual testing. No real support for automated tests.
2) Lack of support for UI-driven/Event-based automation. The only support for automation is via the REST API or project workflows (other tools like IBM DOORS or PTC Integrity have their own scripting language or something called 'triggers')
3) Requirements are not really managed like documents but user stories, i.e. a 'requirement' requires both a title and description but traditionally a requirement is a single statement; this makes the requirements document view not so great (other tools like IBM DOORS or PTC Integrity display requirements as single blocks)
4) The built-in diagraming tool is based on an old version of mxgraph (old and buggy)
5) Filters and Dashboards have limited capabilities.
2) Lack of support for UI-driven/Event-based automation. The only support for automation is via the REST API or project workflows (other tools like IBM DOORS or PTC Integrity have their own scripting language or something called 'triggers')
3) Requirements are not really managed like documents but user stories, i.e. a 'requirement' requires both a title and description but traditionally a requirement is a single statement; this makes the requirements document view not so great (other tools like IBM DOORS or PTC Integrity display requirements as single blocks)
4) The built-in diagraming tool is based on an old version of mxgraph (old and buggy)
5) Filters and Dashboards have limited capabilities.
What problems is the product solving and how is that benefiting you?
1) We use the tool primarily for test management: internal and acceptance (FAT) testing. The tool is used for test suite/case definition, test execution as well as storage of test results (both manual and automated tests) . We have successfully replaced old test management tools and documents/spreadsheets.
2) We use extensive use of the REST API to gather information, automate tasks and generate our own dashboards and metrics.
3) Our current requirements management process is very basic (no heavy users) but we really like the Jama Review Center for formal reviews.
2) We use extensive use of the REST API to gather information, automate tasks and generate our own dashboards and metrics.
3) Our current requirements management process is very basic (no heavy users) but we really like the Jama Review Center for formal reviews.
Recommendations to others considering the product:
Overall Jama Connect is a good solution for supporting Requirements & Test Management within the same tool. It is web-based (no need to install locally), very easy to use and configure, acceptable customizations, traceability (impact/coverage analysis), support for formal reviews (Jama Review Center), integration (REST API) and other features that align with tools like JIRA. It is primarily designed for Requirements Management and still lacks some capabilities as a global Test Management tool (only support for manual testing but it can also be used as a repository of automated test results)
Solid, Flexible Tool Capable of Handling a Large Volume of Projects and Users
What do you like best about the product?
Traceability and the traceability matrix. The ability to establish relationship rules, relate items and item types, and then see where you have gaps is really powerful. After your relationships are established, if you make a change to an item you can see which related items might be impacted. It makes management of requirements extremely easy.
What do you dislike about the product?
Although I like the testing capabilities, the process of setting up test plans, test groups, test cases and test runs is confusing and not very intuitive. Also, although I prefer to keep everything online, we do have customers that want exported copies of requirements. The export capabilities of Jama are somewhat confusing and we have struggled to develop a template that is well-formatted and manageable.
What problems is the product solving and how is that benefiting you?
Prior to Jama we captured requirements in long, cumbersome and complicated Microsoft Word and Excel files. It was hard to get customers to read and understand the proposed solution because of this. It's hard to give someone a complicated, 200 page file and expect them to read it thoroughly.
With Jama we often bring up the tool live with our customers, so we can enter and edit requirements in real time. This gives them instant input into the eventual outputs. In addition, the online review feature provides an easy way to present requirements to customers and get feedback. You can choose to send only a portion of your requirements for approval, which makes it easier for the customers to focus on the content and provides a more iterative approach to requirements gathering and validation. We've seen a dramatic improvement in project delivery after introducing Jama.
With Jama we often bring up the tool live with our customers, so we can enter and edit requirements in real time. This gives them instant input into the eventual outputs. In addition, the online review feature provides an easy way to present requirements to customers and get feedback. You can choose to send only a portion of your requirements for approval, which makes it easier for the customers to focus on the content and provides a more iterative approach to requirements gathering and validation. We've seen a dramatic improvement in project delivery after introducing Jama.
Recommendations to others considering the product:
Create one or more projects to be used as Templates, and then copy those projects to create new projects. Try to keep only a few relationship diagrams so you don't have inconsistency across your project portfolio. Users will adopt Jama more easily if there is this consistency as they switch from project to project.
Great tool that has enabled cross-team collaboration
What do you like best about the product?
Simple to use. All engineers were able to pick up and use the tools with very little learning curve. To everyone of the team, this tool was a breath of fresh air
What do you dislike about the product?
Spell-check doesn't work well when you are first writing the requirements (or any other item). It works when you go back in to edit.
What problems is the product solving and how is that benefiting you?
We are using Jama for our requirements, verification, and risk management. As a young, small company, this was a great tool to help us get the team going with the fundamental task of building requirements. The tool was well received by each of the engineers and is now part of our engineering culture.
Recommendations to others considering the product:
If you can make it fit in your budget, it is definitely worth it
Transformation Shift
What do you like best about the product?
Constant and latest Updates. Willingness to share and work collaboratively
What do you dislike about the product?
Can provide built in reports from the details stored
What problems is the product solving and how is that benefiting you?
All time technical support and right guidance at right time
BL - Cruise Review for Jama Connect
What do you like best about the product?
Cruise Jama supports the traceability functionality we need, and allows us to track approvals with formal signatures. We have had positive response to list view, reading view, trace view, and round trip exports. We have few instances of troubleshooting or outages, and the customer support is generally helpful. Jama has been a staple at Cruise for 3+ years, and we are starting to adopt it as the company's source of truth.
What do you dislike about the product?
Jama UX is not always intuitive, and there's a bit of a learning curve. New users and organizations that are not familiar with Jama have some resistance to adopting Jama. Industry veterans from aerospace, energy, and medical devices are generally pretty accepting and are willing to put in the extra work. Folks from start up background are often not impressed and/or find the "extra clicks" cumbersome. Some of it is them getting used to the idea of more established and traced engineering work; but a big portion of it could be alleviated with a strong focus on UX improvements.
What problems is the product solving and how is that benefiting you?
Like many start ups to medium sized silicon valley companies, we have a hard time aligning on a single source of truth. With Jama, we are getting in the habit of formally recording and approving on a plan of record, and pointing our teammates to a single source of truth.
Seven years of success with Jama
What do you like best about the product?
The review system is easy to use and encourages secondary users to be involved in the requirements process.
What do you dislike about the product?
The system is a little overwhelming when first starting. Example projects (or templates) would be helpful to show a new comer possible document structures. It's been a long time since we started so these examples may exist now.
What problems is the product solving and how is that benefiting you?
We're developing traditional waterfall requirement documents. Being able to export requirements to our test department's tools has been really helpful. Now if we can only get the marketing department to produce documents that can be imported. So, end-to-end traceability. The other thing is, the review system has had the side effect of getting more people involved since it is funner than reviewing a document in an e-mail.
Remote Design Control Center
What do you like best about the product?
JAMA Connect allows my team and I the ability to collaborate in our product design and development. It has a nice user interface that is intuitive and quick for new employees to learn. I also like the API which allows us to sync it with our existing project management tools.
What do you dislike about the product?
I think the risk management could be improved if there was a way for it to automatically calculate risk scores based on severity/probabilities. Right now it all has to be calculated manually.
What problems is the product solving and how is that benefiting you?
JAMA connect lowers the complexity and burden of having to manually keep requirements, architecture, and specifications all in sync and traced to each other. It's a formidable problem that is virtually eliminated courtesy of JAMA without the hassle of having to learn clunky UI (IBM Doors).
Jama Connect allows for a wide variety of uses
What do you like best about the product?
The Review Center and Trace View are the most valuable features. Review Center allows for collaboration with other users and a centralized place to track discussions. The trace view allows me to easily see the full status of all items, and allows that view to be extracted to a spreadsheet for additional manipulation or reporting externally.
What do you dislike about the product?
The dashboards are not per user. Also, it takes a lot of clicks to copy items or create downstream items. The most issues my users have is due to the use of Tasktop for the integration with ADO, as there is no native integration. Tasktop is not a very user-friendly product. Many users think Jama Connect is the issue in such cases, when it's really Tasktop.
What problems is the product solving and how is that benefiting you?
We have less rework, I am able to track requirements over time, and I am able to break down my requirements into individual Agile items easily for the engineers. As I work with a completely distributed team over multiple countries, it is very easy to distribute work and receive feedback and input.
Jama Connect
What do you like best about the product?
Jama's capability for collaboration is foundational in managing requirements.
What do you dislike about the product?
Jama's limited APIs for integrations and performance can be improved.
What problems is the product solving and how is that benefiting you?
Systems engineering supported well by software across large scale organization.
Recommendations to others considering the product:
Great solution for complex projects.
showing 131 - 140