Jama Connect vs. productboard

Jama connect has the best UI compared to DOORS, Codebeamer, and PTC Integrity. It’s the clearest to use with the best usability. For example make traces between all requirements is as straightforward as clicking a button. The trace matrix view is highly configurable to get you to show anything you need. It has extensive filtering where every index in your requirement is indexed. Same with their export features, you can use default templates or create custom templates to export to PDF for all your regulatory needs like submitting documentation to FDA. This has helped us a ton without requiring much edits and letting us create up to date reviewed documents.

Speaking of review system, it’s well organized and you can set required approved and optional reviewers. Track your redlines in the tool and also view and resolve comments.

The one issue I’ve experienced is that with a large system the web app can take some time to load everything.

Incentivized

The best feature of productboard is organized features, it has a very simple structure and can be read and understood by anyone. If your roadmap is very dynamic and the executive team needs to be on top of it, productboard is the best application out there. But if you have a small product and features do not change very often, then maybe you can look at other alternatives since productboard is expensive.

Incentivized

• 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.

Incentivized

• Flexibility - organize your products and features in any way you like
• Input - give your teams a way to make suggestions and provide feedback
• Integrations

Incentivized

• 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.

Incentivized

• The interface could be improved
• Input field options could be less restrictive to the capture of data
• Better notifications / updates on where insights have got to

Incentivized

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

Incentivized

The requirements and baseline parts are easy to use. The review centre is very useable and understandable, once you understand/set up the moderation. (This last part could use some refinement.) Integration/connectability (the Connect part of Jama) is quite possible, but the useability could use some love as well.

Incentivized

It has always been available, except for preventative maintenance which is announced beforehand. Nonetheless, we experienced one day shortage over a miscommunication about payment.

Incentivized

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.

Incentivized

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.

Incentivized

Easy to contact right through their Intercom app and incredibly fast to respond.

Incentivized

Helpful and exhaustive and tailorable for our needs. Instructor was well versed and engaged. Material was a good reference and was up to date with tool. Overall, in person training was valuable for tool introduction. Trainer was an active user of the tool and worked closely with other clients. So, very knowledgeable.

Incentivized

Easy to reference and understand. Updated routinely to include new topics. Online training evolves to include more advanced topics and how to guides. Online training includes videos and reference guides that make it easy to perform more complex tasks. Online training is free and can be accessed from any computer.

Incentivized

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.

Incentivized

JCA is an extraordinary tool that is very simple to use and brings efficiency to the creation of requirements. It is particularly good at highlighting improvements to requirements which, when done properly and done up front in the engineering development process, will save significant time and prevent confusion downstream in the development process. It's difficult to quantify how much of a positive impact JCA would have on any individual project, but I would say it could easily save an organization more than its cost in terms of improving efficiencies and the traceability integrity throughout the entire portfolio of projects when applied correctly. This additional product from Jama is highly recommended.

I have previously used Aha another product road mapping/ insights driven software. Aha had great features for the userbase of my previous products. They were allowed to create their own suggestions for the products and other users could then like or dislike the suggestion. This created a real reflection on need for product enhancements. productboard handles this slightly differently. Each user creates their own suggestions and doesn't necessarily have visibility on other users suggestions. The product/ R&D team can then tag suggestions together into the same overall suggestion. This requires more input from product/R&D with productboard. I would however, suggest that productboard is better than Aha. Aha is great for an external user point of view; however, there may be case for users to not have visibility on wider user requirements. productboard keeps more of this element hidden and would perhaps stir up less negative correlation to seeing a system requirement/suggest having had a lot of traffic and no action, compared to a more closed system that would individually update each user on the enhancement progress.

Incentivized

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.

Incentivized

• One experience that converted an engineer to using Jama Connect was an electronics engineer that was writing test plans. I showed them about how to write "unit" or very discrete tests and then showed them an automatic export to get the document. Thus the authoring of the document effort was taken away, they could focus on defining the test
• Unfortunately I have very much struggled to embed systems engineering, requirements management and Jama Connect as part of the 'ways of working' outside the systems and electronics teams.

Incentivized

• Helps to save us a lot of time collecting feedback.
• Increased efficiency.
• Product prioritization can be done in a faster and more robust way.

Incentivized