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.
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.
Jama
What do you like best about the product?
The Jama tool is good because these is a direct correlation between product requirements and test plans or test cases. this way it can be determined what requirements have test cases associated with them and which requirements do not.
What do you dislike about the product?
If you have requirements, test plans, or test cases existing in other tools or mechanisms, uploading from other source not always work well. Sometimes there appears to be a dependency on the type of words (like a heading) but sometimes that is not the case.
What problems is the product solving and how is that benefiting you?
software testing
Recommendations to others considering the product:
Jama is a good tool to use in order to correlate product requirements to test plans and test cases.
If you have already these existing in other tools or mechanisms, uploading these into Jama is not always straightforward.
If you have already these existing in other tools or mechanisms, uploading these into Jama is not always straightforward.
Great product!
What do you like best about the product?
Easy to organize requirements. Able to specify test cases and define relationships to other items
What do you dislike about the product?
Sometimes not the most easiest software to understand.
What problems is the product solving and how is that benefiting you?
Requirement gathering. Able to keep them organized
Recommendations to others considering the product:
Great tool. try it out!
Jama Review
What do you like best about the product?
Jama is a real wonderful tool to track addition of new features to a software and to enhance existing capabilities. I personally consider a lot of value for this tool in the project management cycle due to the abilities and permissions it can provide. I like the read-only feature of the tool since the specs can be written by one team and the implementing team can just read and access it without changing it.
What do you dislike about the product?
The only dislike I have is the lack of integration support with most of the common agile products. This is a pretty big deal considering the fact that a company can use different tools from different companies to take care of its agile software development process.
What problems is the product solving and how is that benefiting you?
The main business problem solved through Jama is that I can collect customer data and turn it into a feature for a future release of my software.
Recommendations to others considering the product:
I do believe that Jama is a pretty good product to use for agile software development
Great tool
What do you like best about the product?
Easy to configure and fast to use. It has a lot of different options that fit any needs. Everything that may be needed in a project already in Jama. Test management is mostly used and everyone provided great feedback of a tool. Easy to create test cases
What do you dislike about the product?
Not a big amount of reporters. It would be good to have more types of reports.
What problems is the product solving and how is that benefiting you?
Test management and requirements tool
Recommendations to others considering the product:
Just try and you will like it
Jama Product Review
What do you like best about the product?
Exchange, links between items and great review tool.
The Jira integration is also a big advantage in our organization, to track advance of the user stories of the project.
The tools is also very useful to allow us to enter user requirements (even if a better import tool will be great) and to follow, though the links include in Jama, all the tasks needed to be done to fitful this requirement.
The "build your own" report from the different available links are also a way to have different views (customer, developer, specialist, etc.).
And I really like the review, as simple as possible, even if "rights" on user story "blind" some information to people who haven't enough permission (some document linked can't be seen through the review).
The Jira integration is also a big advantage in our organization, to track advance of the user stories of the project.
The tools is also very useful to allow us to enter user requirements (even if a better import tool will be great) and to follow, though the links include in Jama, all the tasks needed to be done to fitful this requirement.
The "build your own" report from the different available links are also a way to have different views (customer, developer, specialist, etc.).
And I really like the review, as simple as possible, even if "rights" on user story "blind" some information to people who haven't enough permission (some document linked can't be seen through the review).
What do you dislike about the product?
Global ID not well manage (moving from a project to an other), as we are working on a product built by projects. So, when we move "user story" from project to the "product" (in fact, an other project), the Global ID is changing, and all links are lost.
The product management must be improved, to be able to "pick up" easily from one project (our product) each function that are useful for a dedicated project, with only "links", and not copy/paste which change this Global ID.
The product management must be improved, to be able to "pick up" easily from one project (our product) each function that are useful for a dedicated project, with only "links", and not copy/paste which change this Global ID.
What problems is the product solving and how is that benefiting you?
Have one tool to describe the function of the solution, and share, with review, to many people around the world.
Recommendations to others considering the product:
Good collaborative tool, with excellent review process.
Integration with Jira is also great.
Integration with Jira is also great.
Worked on few big projects by using Jama
What do you like best about the product?
Requirements, test scenarios, test cases can be collected in one place with relations between them
A lot of report types, which are very useful
A lot of report types, which are very useful
What do you dislike about the product?
Not easy way to move existing test cases
Not easy way to create test plans
Dislike way of TC's links creation for mailing
Not easy way to create test plans
Dislike way of TC's links creation for mailing
What problems is the product solving and how is that benefiting you?
Gathering all basic info about project in one place. Ability to work within Jama (not only reports creation and reading of requirements)
showing 181 - 190