Likelihood to Recommend Jama is an excellent tool for requirements management, development, and traceability throughout the development lifecycle. Jama aids in peer reviews of generated artifacts with time-boxed review cycles. Jama provides a robust ecosystem which is highly tailorable to the demands of the particular organization in which it is used
Read full review We tried the Modern Requirements4DevOps AddIn to see if it brings a added value to our development. I have to say that I would distinguish between types of projects in which it is beneficial and in which it is probably "over engineering". Certainly, bigger development projects with higher complexity are more suitable than small and not really complex projects. However, for the bigger projects Modern Requirements4DevOps definitely helps to deal with the complexity as it adds way more contextualisation to the various entities. It really helps to understand which requirements led to which action in a diagram or task during development. It helps to control the complexity and inform all team members along the project.
Read full review Pros Requirements Management in general Focus in the content without loosing the track of the evolution of the items by maintaining the exchange of information between the users inside the Tool. The possibilities to integrate this tool within our IT-landcape and with our other engineering tools is for us a leverage to success. Read full review Smart Documents Building a connection between individual entities (requirements, documents, tasks, tests) Requirements Management and Reporting Read full review Cons The 'filtering' capabilities in Jama are not as good as they could be. In particular, the ability to "nest" filters is quite limited. I have certain seen much better capabilities in other tools. ('Cradle' is an example of a tool with excellent "nested filters" capabilities.) From an administrative point of view, the 'License' admin view is pretty disappointing. The particular thing that I'd like to be able to find out from it is the peak number of 'Float Creator' licenses in concurrent use on each day. If there's a way to get to that information, I haven't found it yet. Ian Webb Systems Engineering Technical Writer
Read full review forms could be transferred into in line fields to allow in line maintenance of data make window management of diagram builder more flexibility to make more space to build diagrams I would wish that the performance is a bit better sometimes, loading times can be quite long in some cases Read full review Likelihood to Renew Jama is really easy to use and operate compared to other tools. This allows a process owner to get easier buy-in from the organization to see value early. My experience with this tool was very positive and we were able to see value early in its introduction
Read full review Usability Jama is mostly designed for requirement gathering, but that can be possible using
JIRA if we add only approval type of plugin for special requirement types. Jama's performance and features do not improve on a periodic basis i.e. with each release. Even bug fixes take a lot of time and they don't care about customer impact.
Read full review Reliability and Availability Jama is available most of the time if it is used within the application's boundary. Jama has very good availability if we use very high hardware servers. Sometimes we face issues if there are batch operations running.
Read full review Performance With performance compared to
JIRA , I do recommend Jama in this case. Jama provides very good performance, it loads immediately for any of the items and searches any item immediately. Performance is really good in all of the operations including creating stories, epics, item types or other support operations or report generation.
Read full review Support Rating They typically answer within minutes of posting a ticket, and then you have a clear expectation of what the issue is, how to diagnose it, how long will it take to get resolved, and in which version a given problem is resolved, or if there is a patch for hosted services. They have a number of support people, and all of them are top-notch.
Read full review Implementation Rating Jama 2015.5 implementation is very smooth and no need for much manual work. Jama 8 has many challenges and we can not install it as smoothly as Jama 2015.5. Initially, Jama didn't provide the Jama 8's installer files or zip files and they were just providing docker files to everyone (which was really strange). It is the worst that they don't provide all the files at a time. Why should they tell us where we should deploy, and why only a dockerfile? I am not very satisfied with Jama implementation.
Read full review Alternatives Considered The major sellingpoints of Jama were the review-system for internal and external reviewers and the inclusion of (Use Case) modelling tools, while keeping the core requirements-centric. Ability to synchronise with currently in use test-tooling and the low learning curve were additional selling points. Availablity of support in our local language was much appreciated as well.
Read full review Modern Requirements4DevOps is an AddIn for
Azure DevOps Server (Microsoft Azure DevOps) and extends the native features of Azure DevOps in the area of Requirements Engineering, Requirements Management and Reporting. Azure DevOps already contains tons of valuable features. However, for bigger and more complex projects Modern Requirements4DevOps extends Azure DevOps by further features. Thus we used both products alongside.
Read full review Scalability There is no horizontal scalability available in Jama, we have only one choice to scale it vertically. But vertical scalable applications always have limitations to grow. In this case, Jama doesn't support horizontal scalability functions like multi-node architectures with a shared drive for the home directory.
Read full review Return on Investment Made it easier to know what I'm responsible for, from a work task perspective. Allowed leads/managers to assign work in a more educated manner by seeing workload, etc. Allows clear deliverables and more accurate work estimates, since we can look back at previous examples (assuming there are some). Read full review Better communication --> thus less misunderstandings More Transparency about requirements --> adds context and helps to build a common understanding Traceability of Requirements --> we used the baseline also to look into the history of requirements to understand how certain requirements have changed Read full review ScreenShots