TrustRadius
Jama, from the company of the same name in Portland, Oregon, is an application lifecycle management platform.https://dudodiprj2sv7.cloudfront.net/product-logos/vZ/A0/XO12ZA7CTIXE.jpegGot a very complex product? Adopt Jama, it's best for your requirements management!We are basically integration solution provider and have an active partnership with Jama. We help their customers integrate Jama with other systems such as JIRA, Salesforce, Git, Jenkins, TFS, PTC Integrity etc. So, Jama's enterprise-level customers can now synchronize data across systems using the OpsHub Integration Manager, our flagship solution. A possible use case can be integrating Requirements in Jama to Epics in JIRA. So, a product manager creates a requirement in Jama, the JIRA users get an epic created automatically. Any changes made in either of requirement or epic gets synchronized bi-directionally to both the systems. This maintains traceability and data consistency.,Flexibility to create a custom requirement management ecosystem. I love the fact that a Jama user can choose from a large variety of existing entities, but at the same time, also create new components and sort and manage them effectively. One can link different entities, bundle them and segregate them. Traceability Jama focuses a lot on maintaining traceability. And anyone who uses Jama will notice this. For even a delta change in the requirement or entity, it locks in the time stamp and the user. This proves to be a very useful feature in industries where data traceability is critical. Jama is thus best suited for requirement management in industries like aerospace, defense, and healthcare. One can always go back and get the whole audit trail. The Trace View and Reading View In a complex scenario, where one has to manage hundreds of requirements, Jama provides the best way to analyze them. The new features like Trace View and Reading View (which were absent in earlier versions) make requirements management more intuitive. Users can create a custom filter and view as well, this is great.,I think these guys should really work on the User Interface. The UI is intuitive but can be more user-friendly. For an example, color coding the entities according to Priority, Status would be awesome. JIRA does a great job in doing this. Something similar can be done in Jama. Though Jama claims to be a Product Development Tool, it is actually very good at just managing requirements. All the other important aspects have been ignored in Jama (like test suite, bug/defect tracking). This is a reason that other tools like JIRA, Git, HP QC have to be deployed complimentary to Jama. The integration of these tools becomes very important and there are only a few reliable integration solutions available in the market.,9,All the innovation-centric companies are adopting Jama. They have big customers like SpaceX, NASA, Fairchild Semiconductor to name a few. They also have very small companies and startups as their customers. One can conclude that the ROI is surely positive and significant.,PTC Integrity, IBM Rational DOORS and IBM Rational DOORS Next Generation,JIRA Software, Team Foundation Server, Microsoft Visual Studio Team SystemJama ReviewJama is the primary requirement tool used by the BSA team. We're moving over from Agile Central and are in the process of implementing it for all projects. QAs and other departments have just started to use the tool.,Coverage Explorer gives a great view on the complete flow from requirements to tests and defects. Linking between requirements and test assets and defects are intuitive. Release management is pretty good.,We are trying to integrate Jama with SoapUI and haven't found an easy way of handling it. While integrating with Agile central, "one to many" and "many to one" mapping worked. But unable to map "many to many" folders/assets. Support resources available are less.,6,Positive - worked well for waterfall projects. Negative - Still trying to see how it fits for Agile projects.,CA Agile Central (formerly Rally), JIRA Software and HP Application Lifecycle Management,CA Agile Central (formerly Rally), HP Application Lifecycle Management, JIRA SoftwareJama Review for the Curious MindJama started being used as a part of a larger department of 25 people which also served as the "test bed" and "pilot" for cross-company as well as enterprise-wide use (we currently are a company of about 800 that is a part of a bigger corporation consisting of thousands of staff). The business problem it addresses is that it provides far better ability to enter, track, manage and report on software requirements than our previous application. It also solves the age old problem of costly maintenance and customization of tools such as this.,Jama has the keen ability to provide hierarchy for requirements in a collapsible tree style management view allowing for far better reach of information then many of the other system we have used. Jama has the ability to create filters, tags and custom searches in order to better disseminate large scale requirements in order to be able to get from building to testing in less time. Jama possesses the ability to create and link between test assets and have a very intelligible view of managing the bridge between both worlds. It also allows for creation and management of test runs for different iterations of the test cycle; whether it is a dry run, full regression or partial corner case execution. Jama has great ability to create custom output from Excel files to Word which can filter and mine the data from requirements to test assets and present them in different print view for consumption of different audiences and stakeholders in different parts of the teams.,Jama can have better overall SDLC management components especially bridging between different ALM tools. Jama is not an ALM tool but can have some better customization of defect reporting mechanisms as well as test run approach. Jama's ability to break out steps into sub-children in a test plan hierarchy can use a bit of improvement to make it more modular.,9,Jama has brought some new life to our requirements management and how we see the inter-connectivity of functional requirements with System Requirement Specifications which are more UI centric. Jama has brought much better dashboards and reporting for everything it supports from printing test plans, requirements and specifications as well as test runs. Jama has had some challenge in usability as far as training and discovering features we did not know about. There seems to be a different way to do one thing and that is sometimes hard to hone in on how the best approach is. It is more open ended then many other tools like this. Training we have had but it seems that needs to be a repeated period requirement.,IBM Rational DOORS, JIRA Software, HP Quality Center and HP Application Lifecycle Management,IBM Rational DOORS, IBM Rational ClearCase, IBM Rational RequisitePro, HP Application Lifecycle Management, HP UFT, HP Performance Center, HP LoadRunner, Team Foundation Server, Microsoft Visual Studio Team SystemWaterfall Requirements management at its best.Jama was used at my former employer as an internal service offering to all company project teams. It was offered free of charge to any client we were supporting as a requirements management tool and also addressed requirements traceability, defect tracking, test case management, and a data object dictionary in some cases.,Requirements generation and workflow. It's fairly simple to set up a requirements template and create a workflow for progression. Hierarchical categorization. While it may not seem like a big deal but the ease of which you can create parent child relationships makes it easy to group similar requirements (user stories) under related epics or folders. This is very helpful when trying to visualize at a glance what releases contained which features and not something some Agile tools are very good at..ahem...Jira.,Requirements traceability. While it does offer some pretty good traceability options it could benefit from more dynamic updates. (e.g. If all my downstream requirements are "met," how about auto updating a status field in the upstream requirement so I can tell the larger item (epic) is complete? Jama-Jira connector was spotty at times. We used this to connect high level requirements down to the agile teams that were working on them, synchronization seemed to be working about 85% of the time. Project administrators don't have enough permissions. For example you need to be a Jama administrator [or] a project admin to create workflow for your particular project. You also cannot customize object types (e.g. a requirement). I don't know any two projects that use all the same fields.,6,Faster, more accurate reporting. Prior to one of the projects I worked on, requirements traceability reporting was a manual asynchronous affair. That is to say whenever there was an update we had to make sure all of our spreadsheets were up to date. Jama did wonders for our requirements integrity from that sense, and made it much easier to generate various reports depending on what was being asked.,JIRA Software,JIRA Software, LeanKit, Jive Team Collaboration
Unspecified
Jama
10 Ratings
Score 7.8 out of 101
TRScore

Jama Reviews

Jama
10 Ratings
Score 7.8 out of 101
Show Filters 
Hide Filters 
Filter 10 vetted Jama reviews and ratings
Clear all filters
Overall Rating
Reviewer's Company Size
Last Updated
By Topic
Industry
Department
Experience
Job Type
Role
Reviews (1-4 of 4)
  Vendors can't alter or remove reviews. Here's why.
No photo available
January 09, 2018

Review: "Got a very complex product? Adopt Jama, it's best for your requirements management!"

Score 9 out of 10
Vetted Review
Verified User
Review Source
We are basically integration solution provider and have an active partnership with Jama. We help their customers integrate Jama with other systems such as JIRA, Salesforce, Git, Jenkins, TFS, PTC Integrity etc. So, Jama's enterprise-level customers can now synchronize data across systems using the OpsHub Integration Manager, our flagship solution.

A possible use case can be integrating Requirements in Jama to Epics in JIRA. So, a product manager creates a requirement in Jama, the JIRA users get an epic created automatically. Any changes made in either of requirement or epic gets synchronized bi-directionally to both the systems. This maintains traceability and data consistency.
  • Flexibility to create a custom requirement management ecosystem.
  • I love the fact that a Jama user can choose from a large variety of existing entities, but at the same time, also create new components and sort and manage them effectively. One can link different entities, bundle them and segregate them.
  • Traceability
  • Jama focuses a lot on maintaining traceability. And anyone who uses Jama will notice this. For even a delta change in the requirement or entity, it locks in the time stamp and the user. This proves to be a very useful feature in industries where data traceability is critical. Jama is thus best suited for requirement management in industries like aerospace, defense, and healthcare. One can always go back and get the whole audit trail.
  • The Trace View and Reading View
  • In a complex scenario, where one has to manage hundreds of requirements, Jama provides the best way to analyze them. The new features like Trace View and Reading View (which were absent in earlier versions) make requirements management more intuitive. Users can create a custom filter and view as well, this is great.
  • I think these guys should really work on the User Interface. The UI is intuitive but can be more user-friendly. For an example, color coding the entities according to Priority, Status would be awesome. JIRA does a great job in doing this. Something similar can be done in Jama.
  • Though Jama claims to be a Product Development Tool, it is actually very good at just managing requirements. All the other important aspects have been ignored in Jama (like test suite, bug/defect tracking). This is a reason that other tools like JIRA, Git, HP QC have to be deployed complimentary to Jama. The integration of these tools becomes very important and there are only a few reliable integration solutions available in the market.
Jama is best suited for industries with complex products. These include industries like aerospace, semiconductor etc. Also, industries where data traceability is important - like healthcare, defense etc.

A product like Jama, according to me, is not useful for scenarios where inter-team dependency is minimal or the product developed is not very complex. One does not require a powerful tool like Jama there and a very basic requirement management tool would suffice.
Read this authenticated review
No photo available
March 27, 2018

"Jama Review"

Score 6 out of 10
Vetted Review
Verified User
Review Source
Jama is the primary requirement tool used by the BSA team. We're moving over from Agile Central and are in the process of implementing it for all projects. QAs and other departments have just started to use the tool.
  • Coverage Explorer gives a great view on the complete flow from requirements to tests and defects.
  • Linking between requirements and test assets and defects are intuitive.
  • Release management is pretty good.
  • We are trying to integrate Jama with SoapUI and haven't found an easy way of handling it.
  • While integrating with Agile central, "one to many" and "many to one" mapping worked. But unable to map "many to many" folders/assets.
  • Support resources available are less.
Well suited
-Waterfall model requirements
-Coverage Explorer
-Requirements-Test Assets-Defects mapping

Less suited
-Scrum/Agile
Read this authenticated review
Fred Sookiasian profile photo
September 20, 2017

"Jama Review for the Curious Mind"

Score 9 out of 10
Vetted Review
Verified User
Review Source
Jama started being used as a part of a larger department of 25 people which also served as the "test bed" and "pilot" for cross-company as well as enterprise-wide use (we currently are a company of about 800 that is a part of a bigger corporation consisting of thousands of staff). The business problem it addresses is that it provides far better ability to enter, track, manage and report on software requirements than our previous application. It also solves the age old problem of costly maintenance and customization of tools such as this.
  • Jama has the keen ability to provide hierarchy for requirements in a collapsible tree style management view allowing for far better reach of information then many of the other system we have used.
  • Jama has the ability to create filters, tags and custom searches in order to better disseminate large scale requirements in order to be able to get from building to testing in less time.
  • Jama possesses the ability to create and link between test assets and have a very intelligible view of managing the bridge between both worlds. It also allows for creation and management of test runs for different iterations of the test cycle; whether it is a dry run, full regression or partial corner case execution.
  • Jama has great ability to create custom output from Excel files to Word which can filter and mine the data from requirements to test assets and present them in different print view for consumption of different audiences and stakeholders in different parts of the teams.
  • Jama can have better overall SDLC management components especially bridging between different ALM tools.
  • Jama is not an ALM tool but can have some better customization of defect reporting mechanisms as well as test run approach.
  • Jama's ability to break out steps into sub-children in a test plan hierarchy can use a bit of improvement to make it more modular.
Jama is well suited for smaller to mid size companies from my usage and time spent with it and I can see it as a powerful tool possible for larger ERP scale implementation of systems. However, in those situations, some companies may prefer an all-around ALM suite especially linking business process components to BPT testing and other gateways to automation. That may be an issue since Jama is a bit flat in the ability to support and link to provide that level of throughput for ALM implementation.
Read Fred Sookiasian's full review
Jason Hall profile photo
January 08, 2016

Jama Review: "Waterfall Requirements management at its best."

Score 6 out of 10
Vetted Review
Verified User
Review Source
Jama was used at my former employer as an internal service offering to all company project teams. It was offered free of charge to any client we were supporting as a requirements management tool and also addressed requirements traceability, defect tracking, test case management, and a data object dictionary in some cases.
  • Requirements generation and workflow. It's fairly simple to set up a requirements template and create a workflow for progression.
  • Hierarchical categorization. While it may not seem like a big deal but the ease of which you can create parent child relationships makes it easy to group similar requirements (user stories) under related epics or folders. This is very helpful when trying to visualize at a glance what releases contained which features and not something some Agile tools are very good at..ahem...JIRA.
  • Requirements traceability. While it does offer some pretty good traceability options it could benefit from more dynamic updates. (e.g. If all my downstream requirements are "met," how about auto updating a status field in the upstream requirement so I can tell the larger item (epic) is complete?
  • Jama-JIRA connector was spotty at times. We used this to connect high level requirements down to the agile teams that were working on them, synchronization seemed to be working about 85% of the time.
  • Project administrators don't have enough permissions. For example you need to be a Jama administrator [or] a project admin to create workflow for your particular project. You also cannot customize object types (e.g. a requirement). I don't know any two projects that use all the same fields.
Jama works better for a traditional (aka waterfall) style application lifecycle style project. If your environment is primarily operating under an agile methodology, there are better tools out there. If you have to generate repeated requirements traceabily reports, this is your tool.
Read Jason Hall's full review

Jama Scorecard Summary

About Jama

Jama, from the company of the same name in Portland, Oregon, is an application lifecycle management platform.

Jama Technical Details

Operating Systems: Unspecified
Mobile Application:No