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.
Ideal tool for tracking requirements for product updates.
What do you like best about the product?
Jama is an ideal tool to keep track of the useful life of a product x, thanks to this tool you can determine certain characteristics and requirements of a product, with the tools available to Jama, a complete analysis can be made and technician of the improvements that are desired to be made, when they should be done, and how they should be done, the continuous monitoring of the products being analyzed is an ideal part of the application, which allows to evaluate the percentage of risk and defects that may exist during the life cycle of the same, thanks to all this type of characteristics can be made different analyzes or tests with different data and sources, to determine the faults that may exist in the future.
What do you dislike about the product?
The explorer who is responsible for making a coverage of elements is limited to a maximum number of them, which should be something unlimited, and have a total coverage of all the elements that need to be analyzed, I do not see why have a limit in this field, is something unnecessary, something that I do not like about this application is the generation of reports, these when you see them inside the application, they look very good, but when you download them and open them with other programs on the computer, it becomes a Chaos, and everything seems to be messy, is something that should be improved as soon as possible.
What problems is the product solving and how is that benefiting you?
With this application build a working group that is responsible for developing a follow-up to the different products of our company, which provides us with clear reports, defects and failures, in which we may be falling, without realizing, we also take care of to analyze new products of the market, and see the positive or negative impact they can have within our company, and the advantages we can have with them, in front of our competitors.
Recommendations to others considering the product:
You must have a clear idea of what you want in your company before purchasing this product, make sure it is suitable for your needs.
Newbie
What do you like best about the product?
The flexibility to mould Jama to work with different project needs. Has become a wiki for us too.
The structure aligns with our need to export to Word for wider review and distribution
The structure aligns with our need to export to Word for wider review and distribution
What do you dislike about the product?
The limited functionality of Word mail merge. It's a shame reporting/documents that add real value need a different skill set.
When selecting a tag to view related items, the folder structure is lost. This is a shame as it would enable us to export a subset of data but keep the headings (folders) in any document
When selecting a tag to view related items, the folder structure is lost. This is a shame as it would enable us to export a subset of data but keep the headings (folders) in any document
What problems is the product solving and how is that benefiting you?
Traceability from business case and benefits through multiple levels of requirement definition through to testing.
It takes a bit of learning to fully get benefits from the filters and mail merge functionality but it is working for what we need it to do.
It takes a bit of learning to fully get benefits from the filters and mail merge functionality but it is working for what we need it to do.
Provisioned Jama in AWS ECS Cluster
What do you like best about the product?
Features in the product
Ease of use, review and comments options
Generate reports
Ease of use, review and comments options
Generate reports
What do you dislike about the product?
Deployment was complex if you need to deploy in ECS cluster.
What problems is the product solving and how is that benefiting you?
Features tracked from BRD to Testing
Using Jama Connect has brought a much broader stream of our workflows into a single tool.
What do you like best about the product?
Using Jama Connect has provided the ability to perform detailed impact assessments from a single source, expediting the process and reducing the mistakes made between disparate data sources.
What do you dislike about the product?
While Jama Connect provides many useful features, some are implemented at a basic level and are constrained in ways that do not fit our current practices. I know Jama is working to enhance the product and look forward to resolving these wishes.
What problems is the product solving and how is that benefiting you?
We needed to bring our requirements management, defect management, and test management processes into a single tool in order to ensure impact and relational context was easily viewed.
Product requirements with Jama
What do you like best about the product?
Jama made creating product requirements simple. When you have a complex product and you need to work collaboratively with the team, you have one place to do it, virtually accessible from anywhere. It starts with a project and then you have a nice and friendly User Interface to add more: marketing/automotive/functional/business/high level requirements, all kinds of notes and many more, each of them with predefined template.
What do you dislike about the product?
As an admin of Jama Connect I am responsible with permissions also. The integration we have is with our local Active Directory but adding people from AD to Jama has to be one by one, there is no way in the current setup to go by user groups and make my life easier.
Our requirements for reporting (in any tool for that matter) are more complex than Jama can offer.
The cost of the tool is per user and we find it incovenient some time to manage the inactive users, just to make room for the new.
Our requirements for reporting (in any tool for that matter) are more complex than Jama can offer.
The cost of the tool is per user and we find it incovenient some time to manage the inactive users, just to make room for the new.
What problems is the product solving and how is that benefiting you?
We use Jama Connect in our marketing department where they need a tool to help them build product requirements. They need collaboration, reviews, approvals on each individual item. Jama Connect seemed to be a good match and that was the reason why we selected it.
Recommendations to others considering the product:
Go for Jama Connect when you have a budget to spend and need a complex tool for managing non technical project requirements. You will get a nice user experience, an easy to use tool.
Jama - Mordern Requirements Management solution
What do you like best about the product?
Captures requirements efficiently, pretty good requirements traceability options, baseline requirements easily, different views available, AGile ready, version tracking, test cases development, detailed workflows for estimation and manage project schedule.
What do you dislike about the product?
Jama-JIRA connector was failing at times, training, FAQ material seems outdated, admins do not have enough permissions
What problems is the product solving and how is that benefiting you?
Used it to capture requirements and managed testing. The container model for managing requirements is both easy to understand and to use. You can track the requirements through different phases, backwards and forwards as well as dependencies across requirements.FAQs and user guide could have been more exhaustive. Will surely use Jama in my future projects.
Business Analyst using Jama for requirements in small IT company
What do you like best about the product?
After years of producing requirements in Word documents using track changes and versioning, there are several features of Jama that I really appreciate. My favorite feature, however, would have to be the review center. It is a nice, efficient way to share requirements, receive feedback, and compare versions of requirements. Everyone can participate in the review process and communicate with each other in an effort to finalize requirements.
What do you dislike about the product?
I had to search for something I felt strongly enough about to say I disliked it.... But I would say the rich text functionality seems a little limited and the use of tables within a rich text field is somewhat awkward.
What problems is the product solving and how is that benefiting you?
We are capturing our business requirements for a new product, and we are very pleased with the improved efficiency and the ease of communication Jama provides us. Keeping everyone on the same page with requirements content and status plus having everything in one, easy to navigate repository has been very helpful.
Recommendations to others considering the product:
If interested in an extremely configurable product to suit your process and development needs, regardless of the industry, I would highly recommend Jama because of the benefits it has provided our team. It has helped to increase our productivity and communication, and it has been embraced by our entire team.
Great Potential Despite Issues with Usability
What do you like best about the product?
Document Management and Search:
The ability to organize many different types of documents, relate them together, search, reuse, and cross reference is very powerful. JAMA is attempting to give you the ability to manage all records (change requests, design docs, bugs, and even test plans) within a single tool. Search is very fast and you have the ability to save and favorite numerous filters.
Communication:
JAMA fully supports good communication in the form of streams, comments, change requests, and even upstream change notification. If you need to be informed and keep up to date with project changes, JAMA can make this largely hassle free.
System Administration:
We have had very little issue with managing hundreds of users on a single system with a pretty average VM host. With the new docker mode (introduced in 2016) upgrades and management are even easier. You also have the option of a cloud based/hosted solution if you prefer.
The ability to organize many different types of documents, relate them together, search, reuse, and cross reference is very powerful. JAMA is attempting to give you the ability to manage all records (change requests, design docs, bugs, and even test plans) within a single tool. Search is very fast and you have the ability to save and favorite numerous filters.
Communication:
JAMA fully supports good communication in the form of streams, comments, change requests, and even upstream change notification. If you need to be informed and keep up to date with project changes, JAMA can make this largely hassle free.
System Administration:
We have had very little issue with managing hundreds of users on a single system with a pretty average VM host. With the new docker mode (introduced in 2016) upgrades and management are even easier. You also have the option of a cloud based/hosted solution if you prefer.
What do you dislike about the product?
Usability:
Though many improvements have been made, there are still a number of general usability issues with reviews (more on that below), filters, and editing. The complete lack of a project wide refactor (search/replace) is just one example of a missing feature that would greatly improve usability. Another example would be per-project pick lists. Large pick lists (over 100) are also not very usable which is why having pick lists per project would improve things a great deal. Another usability issue is dealing with empty values is not consistent in search tools or batch update.
Multi-Project vs Single Project:
It seems as if a misstep was made early on in JAMA development in terms of how things would/should work cross-project. For the most part, you will have the most intuitive experience if you place all related items within one project (sharing a set of versions) but if the project gets too big, JAMA pushing you toward breaking it up because large projects are slow. The problem is, cross project search, navigation, and reporting are limited in some ways and can be confusing for most users.
Review Model:
I feel the review model is simply non-functional. If you are looking for JAMA to implement and enforce good reviews, I would suggest to look elsewhere. Reviews are too complex and review moderators cannot control which changes require re-review so every single change (adding a comma or fixing a spelling mistake) always require 100% re-review from all participants. This is just not workable in my opinion.
Though many improvements have been made, there are still a number of general usability issues with reviews (more on that below), filters, and editing. The complete lack of a project wide refactor (search/replace) is just one example of a missing feature that would greatly improve usability. Another example would be per-project pick lists. Large pick lists (over 100) are also not very usable which is why having pick lists per project would improve things a great deal. Another usability issue is dealing with empty values is not consistent in search tools or batch update.
Multi-Project vs Single Project:
It seems as if a misstep was made early on in JAMA development in terms of how things would/should work cross-project. For the most part, you will have the most intuitive experience if you place all related items within one project (sharing a set of versions) but if the project gets too big, JAMA pushing you toward breaking it up because large projects are slow. The problem is, cross project search, navigation, and reporting are limited in some ways and can be confusing for most users.
Review Model:
I feel the review model is simply non-functional. If you are looking for JAMA to implement and enforce good reviews, I would suggest to look elsewhere. Reviews are too complex and review moderators cannot control which changes require re-review so every single change (adding a comma or fixing a spelling mistake) always require 100% re-review from all participants. This is just not workable in my opinion.
What problems is the product solving and how is that benefiting you?
Having all the design and test definitions easily searchable and stored in a single application is a huge improvement over a document repository (i.e. file share or SharePoint). Two areas that have shown improvement are better communication and greatly improved document reuse.
JAMA Requirements
What do you like best about the product?
JAMA provided a good product for creating and validating requirements. It was easy to share requirements across products.
What do you dislike about the product?
It was difficult to share requirement information with people who did not have a JAMA license. This made the review process difficult to manage. If you are using the product you have to use the whole product not just parts.
What problems is the product solving and how is that benefiting you?
Requirement Management - was a great system for creating and maintaining requirements in a regulated business.
Recommendations to others considering the product:
If you are using this software - use the entire suite - but get the buy in from validation and development groups.
Jama is a really good tool for managing requirements
What do you like best about the product?
Configurability of the system - state transitions, item relationships, directory/tree, form fields
Review center and how all the feedback history is captured in one place
Integration with Jira
Review center and how all the feedback history is captured in one place
Integration with Jira
What do you dislike about the product?
The price! It's probably the most expensive tool we have (cost/user license) so it is never a certainty that we'll keep renewing. Would like to see some flexibility on pricing depending on the features you use. We don't use the test case mgmt features at all, for example. Most products have pricing tiers and it would be nice to see Jama implement that.
I think the reqts management features are pretty strong. Our QA team didn't give the test case mgmt features the thumbs up. They chose Test Rail. So I lost the ability to connect reqts to test cases in one tool. I suggest looking at the test case and test plan features and make those stronger.
I think the reqts management features are pretty strong. Our QA team didn't give the test case mgmt features the thumbs up. They chose Test Rail. So I lost the ability to connect reqts to test cases in one tool. I suggest looking at the test case and test plan features and make those stronger.
What problems is the product solving and how is that benefiting you?
Documenting requirements in one place, in a standard way.
Documenting feedback from stakeholders in one place.
I wanted one source of truth for requirements.
Avoid rework due to missed reqts.
Benefits
Rework due to missed reqts is down (haven't measured by how much though).
BAs are more consistent in how they manage reqts.
History of feedback saves time (discussions about why we did something or what the reqts were in the first place are reduced).
Documenting feedback from stakeholders in one place.
I wanted one source of truth for requirements.
Avoid rework due to missed reqts.
Benefits
Rework due to missed reqts is down (haven't measured by how much though).
BAs are more consistent in how they manage reqts.
History of feedback saves time (discussions about why we did something or what the reqts were in the first place are reduced).
Recommendations to others considering the product:
The change management involved in rolling out a tool like this was bigger than the effort to learn the tool. You need a proper project plan and a capable project manager to get all the internal stakeholders plus external contacts (reqts stakeholders) to buy in, get trained, use it properly, etc.
showing 161 - 170