Reviews (1-9 of 9)
- Product requirements: a nice and easy way of writing requirements, keeping them classified and organized
- Requirements review: the information to review is displayed intuitively in the User Interface and adding your review comments is enabled for every line item in an individual paragraph
- Administration: for a cloud application the administrative features are extensive with an acceptable level of details
- User roles and permissions: I would like to use the company's Active Directory groups when granting permissions for projects. We have it integrated with Okta, however, I can only add people to Jama one by one.
- Out of the box reporting - you can never have enough reporting or custom reporting capabilities. However. Jama has just several and only on demand. Automatic scheduling of reports is not there.
- For more complex requirements you may find it a little difficult to use Jama.
- Price may be an issue for many. It is a cost per user and it is more expensive that other cloud tools we use, with a bigger ROI than Jama.
- Requirement traceability and relationship flow. There are many different ways to show your coverage, flow of requirements, and where they are in a larger perspective of the project.
- Review communication through the review engine is particularly well done.
- Ease of using the system - the ergonomics is excellent. My users have an easy time getting used to working with otherwise complicated structures and organization.
- The ability to pull information from different angles is excellent. The filters are very useful and other products don't compete here like Visure, Doors, etc...
- The initial dashboard is very limited in functionality and views. The bar charts and pie charts are useful but quite cumbersome given you have to specify your filters beforehand. This is very important in my opinion as this is the top level summary that 90% of your management will only look at.
- Coverage explorer - only 150 items at one time. This should be expand to all...
- Verification and Validation need improvement on being able to package and coordinate test runs, cycles, and platform variations of these items. This is a bit cumbersome and difficult for beginner users to get used to.
- It is very annoying and counterproductive that the users have to directly click "logout" to open up licenses. Admins can't boot people out of the system actively to fix if someone has to go home. You have to wait for 2hrs + for their license to expire.
- Create/Edit licenses not defaulting to collaborator licenses is also very annoying for admins especially during very large concept stage input/reading efforts into Jama.
Jama Administrations - I am Working as a Jama Consultant and recommend Jama for various Project Management, Traceability and Test Management tools across Organizations. I provide a complete demo on Jama usage comparing with other tools and recommend Jama.
- Managing around 150 + Projects on the LifeScience Industry - Teams are very much involved completely on the Jama Testing / Traceability and the reports - We recently implemented Velocity reports on our Regulated Instances and Customers are very happy on the Output.
- We have Integrated with Major Project Management application JIRA - Using the Tasktop Integration Hub and the sync works well.
- We also Integaretd with HP ALM with Jama using the JIH and the complete Bsuiness Processes / BPAC, Configurational Items are used by Many Projects.
- Discovery of Customer current and desired future state Product Delivery approach and processes.
- Great Question -Jama Itself is a great tool but coming to the Testing Plan and Test Cycles it needs further improvements on the complete Testing cycle Managements
- Customers from different environment always compare the tools with other Products - Compare to HP ALM the testing functionality needs to be much enhanced in Jama
- Jama is easy to use. Didn't require any training. All plug and play. Easy to enter and maintain requirements.
- Search ability is great - easy to find requirements and provide traceability.
- I love the email notifications - I get notified once a requirement is updated, or when I'm mentioned by name. Makes it easy to create a task list of my "to do's" for my projects.
- Get the enterprise license - this will allow multiple users to access Jama congruently. If not, it's not a true requirements collaboration tool.
- Great for a Microsoft environment, but if you're not using Office tools such as Word or Excel, that could be problematic for reporting. Also requires some reformatting once downloaded into Excel.
- 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.
-Waterfall model requirements
-Requirements-Test Assets-Defects mapping
Jama Connect Review: "Got a very complex product? Adopt Jama, it's best for your requirements management!"
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.
- 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.
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.
- 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.
- 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 Connect Scorecard Summary
About Jama Connect
Jama Connect Screenshots
Jama Connect Videos (2)
Jama Connect Downloadables
Jama Connect Integrations
Jama Connect Competitors
Jama Connect Customer Size Distribution
|Small Businesses (1-50 employees)||0%|
|Mid-Size Companies (51-500 employees)||30%|
|Enterprises (> 500 employees)||70%|
Jama Connect Support Options
|Free Version||Paid Version|
|Video Tutorials / Webinar|
Jama Connect Technical Details
|Deployment Types:||On-premise, SaaS|
|Operating Systems:||Windows, Linux, Mac|