Jama Connect (Private Offer Only)
Jama Software (Private Offer Only)Reviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
186 reviews
from
External reviews are not included in the AWS star rating for the product.
Indispensible to managing business and software requirements
What do you like best about the product?
The software is pretty robust. We have experienced few problems, and when we do, they have top-notch Level 1 and Level 2 support; also because we are an international company, the fact that the have EU support, etc. is also quite helpful.
What do you dislike about the product?
While the Jama community is an excellent way to ask questions and suggest "enhancements," I think some are a bit slow to come to market. For example, easier ways to make MS-Word output and Jama perform more seamlessley.
What problems is the product solving and how is that benefiting you?
Great flexibility and a way to track and integrate sofware and business needs.
Jama Software Review
What do you like best about the product?
Very configurable. Review process is good
What do you dislike about the product?
Review process is not tied to fields in items
What problems is the product solving and how is that benefiting you?
Keeping track of engineering requirements. It is easier to structure and version requirements and documents
Recommendations to others considering the product:
Spend time learning and configuring your system. Make use of the custom item types. Make use of the review process. Spend time on a relationship mapping between item types.
Requirements & Test Case management made easy with Jama.
What do you like best about the product?
Jama has an intuitive interface that makes it easy to capture requirements and test cases, review, and manage relationships. Jama is simple to use but powerful to meet your needs.
What do you dislike about the product?
As a medical device manufacturer, we are required to validate our software. If Jama could provide test protocols to conduct this validation that would be great.
What problems is the product solving and how is that benefiting you?
Jama allows us to capture requirements, product risks, and test cases and then relate them together in order to create a Trace Matrix. In the past, this was a manual, cumbersome, time-consuming process.
Easy to Use Platform which has proven benefical to the business for years
What do you like best about the product?
I like the permissions structure, which is straightforward and easy for users to understand.
What do you dislike about the product?
I would like more administrative functions to help determine if a Jama project is still active. Maybe reminders to project/content owners to update/archive content/projects.
Also a tool to help with inactive users to help manage licenses would be great.
Also a tool to help with inactive users to help manage licenses would be great.
What problems is the product solving and how is that benefiting you?
We use Jama to manage the changes to product documentation and in some cases document collaboration.
Recommendations to others considering the product:
Great product for requirements management and document collaboration.
Jama Product Feature Management
What do you like best about the product?
I like the ability of Jama to manage all related projects with robust synchronization tools. In addition the custom feature matrix report we had Jama create has been working very well for managing all EFI Fiery programs.
What do you dislike about the product?
It took several iterations to get the custom feature matrix report working. In addition, I have been hearing feedback from EFI users of Jama that there should be improved synchronization of one item to many projects. I have also heard search and replace tools can also be improved.
What problems is the product solving and how is that benefiting you?
Jama is the primary Fiery feature management tool. It is used to create master templates for our codebases and making customized projects based off these templates. In addition, Jama feature management is also tied to our automation tools to ensure each product as the correct feature set.
Recommendations to others considering the product:
Make sure you have very specific requirements on what is needed.
Jama upgrade
What do you like best about the product?
The Customer support is responsive and detailed
What do you dislike about the product?
Moving to Jama 8 is a BIG change. In general, I have stayed away from docker. I've heard some painful tales about it and it seems to be a solution in search of a problem that I don't have.
What problems is the product solving and how is that benefiting you?
Consensus around requirements and priorities
Recommendations to others considering the product:
Jama has strong opinions about using their hosted solution. Give it some thought, but chart your own course.
Very collborative and productive platform for requirements and bugs management
What do you like best about the product?
Traceability between requirements, artifacts, change requests, bugs all in one platform in addition to customizable workflows.
What do you dislike about the product?
Standard reports can be enhanced including KPIs and insights
What problems is the product solving and how is that benefiting you?
Managing onshore-offshore SDLC cycle. JAMA offers us a centralized highly collaborative platform.
Fully featured... but still as complicated as the process typically requires
What do you like best about the product?
The JAMA feature I use the most and find the most convenient is the document review. With a distributed team of opinionated individuals, the need for a thorough review process is key. Our team finds the JAMA review capability to fit well into our requirements management processes.
What do you dislike about the product?
Though I find JAMA a good place to review and archive requirements, I rarely develop the requirements within the application itself. There is so much structure and button clicking to create and reorganize items, that I simply just use excel, word, or google docs for the first few rounds of requirements development. The freedom i get in those mediums, including the ability to share and get initial rounds of feedback, just isn't matched by JAMA.
Another issue that we typically run into is difficulty tracking review comments and resolutions between review versions. Often we want users to be able to see the changes that were made based on their suggestions, but the review process makes that difficult to accomplish.
Finally, it would be helpful if the outline numbering that appears during reviews was carried into other places within the tool so that those IDs could be used as references.
Another issue that we typically run into is difficulty tracking review comments and resolutions between review versions. Often we want users to be able to see the changes that were made based on their suggestions, but the review process makes that difficult to accomplish.
Finally, it would be helpful if the outline numbering that appears during reviews was carried into other places within the tool so that those IDs could be used as references.
What problems is the product solving and how is that benefiting you?
The primary problem we are solving with JAMA is requirement and test case baselining. Typically we will do our requirements development outside of the tool, but then we can import into JAMA as baseline from which to work. Similarly, for test cases we develop an initial draft outside and then bring it into JAMA. Having these baselined versions of our systems engineering process make traceability simpler.
Once we have our test cases baselined, we have also benefited from the ability to execute and document test runs/cycles that serve as reviewable artifacts. These artifacts can be simply reviewed to assess test coverage and release readiness.
Once we have our test cases baselined, we have also benefited from the ability to execute and document test runs/cycles that serve as reviewable artifacts. These artifacts can be simply reviewed to assess test coverage and release readiness.
Recommendations to others considering the product:
In the realm of requirements management tools, I'm not sure that the silver bullet we're all looking for exists. The solution to that is probably more human than software. However, as one must often use a formal tool, I would recommend JAMA as an option. The ability to track requirement states, perform reviews, and track test cycle executions are specific features I find useful within JAMA.
We use JAMA for requirements and test case management.
What do you like best about the product?
The idea is nice, but I dread using the tool. I like that it connects into JIRA in some fashion. This way you can track to work you're doing against a test case or a requirement.
What do you dislike about the product?
It's not easy to search, it doesn't really correlate test cases to requirements that well. Can never figure out how to switch between related projects. And, if you want a report to come out of it, you can't. A PDF of test cases or requirements in a readable format so a new person can come up to speed. No. Doesn't happen.
What problems is the product solving and how is that benefiting you?
It's just another tool. It's not helping more than any other tool.
Recommendations to others considering the product:
You need a tool. This one is ok. I don't know that you would use it over DOORS.
Good Requirement tracking.
What do you like best about the product?
The interface is pretty straight forward. Easy to track the requirement along with the test cases prepared to accommodate those requirements.
What do you dislike about the product?
The integration between JAMA and Excel when there is a heavy manual testing done with the help of Excel, it is one tough task to integrate those two.
What problems is the product solving and how is that benefiting you?
Requirement and defect tracking.
showing 161 - 170