I think it's a good and enterprising one. It's good for some people, and some say it is expensive. But for me, I have to say I don't consider finance because that's not my level, but from a usability perspective, I think it is good.

We haven't used the full functionality of the solution yet. We have only used the tracking for a couple of the applications. We haven't used it widely. We are expecting to upgrade the solution and we may use it more after upgrading.

I would rate this solution as an eight out of ten. 

I would give RQM a rating of nine out of ten.

The main competitor of IBM's test management tool is Quality Center. I feel they may have a more user-friendly interface.

However, IBM offers a very good management tool and it's integrated well with the different tracking and design testing solutions. 

I'd rate the solution eight out of ten.

From a reliability and scalability perspective, it's a good tool. It's well-structured. If they did some upgrades to the interface, it would be just about perfect and I'd rate it closer to nine or nine and a half.

Consider the introduction of the tool in terms of the proper education of the teams who will adapt it. I think any introduction of such a tool requires proper training. It's not so intuitive that people can trust it. If you just give it to people directly, without any training, then they can get it wrong. Make sure to invest in training

Smooth integration with JIRA, but I think this is not realistic.

The IBM suite is kind of independent and it's getting more niche because it's not such a big community of users.

I would rate it a seven out of ten. 

This tool would be great if it was used with a package (IBM CLM, includes DNG, RQM, and RTC, as major tools).

Tweak your testing process. It is also better to align the organization in terms of how the tool works.

It is a very good choice on ensuring the expected software quality for projects.

Plan the training and usage properly. Also, proper planning of the architecture and test execution artefacts needs to be dond.

I would rate this solution an eight out of ten.

I suggest to go for other tools. As the number of test cases grow, it’ll be really difficult to maintain the test cases. The tool should be able to support and maintain the test cases in a folder-wise structure to identify the different module test cases.