It's a business process requirement and is being used for test cases, test executions, defect locks, metrics, dashboards, etc.
In implementation projects, things work in the waterfall methodology so it's the best tool to collect all the requirements in one place to tie up into the test cases and test executions, so this solution is extensively being used in the company for implementation projects, particularly in test management activities.
I like all the features this solution provides. It is a good stand-alone test management tool.
Pricing could be improved as it's high-priced. I don't exactly know the pricing point, but previously, I know that it was really high so fewer people were able to use it for their projects. That's the only disadvantage I could think of.
One other thing: I'm not sure if Micro Focus ALM Quality Center has this feature, or other people could be using this feature currently, but if it can be connected to any automation tool then it can pass those automation test scripts, which internally it can reflect that requirement if it passed. If that feature is there, then it's good.
If that feature isn't available, what I would like to see right now is whether it can be done manually. You can say that manually, these test cases that are linked to the requirement have passed.
If this solution, on the other hand, can be connected to an automation tool, then it can update us automatically about the test script and whether there's a link between the test scripts and the requirement, then we can say: "Okay, this requirement ran automation test scripts and it passed, and that means coverage is good."
I don't know whether this feature is currently available. If it's there, good. If it isn't, then that would probably be one last item I would be looking for which I'd like to be integrated into the test management tool.
I'm currently using the Micro Focus ALM Quality Center.
About the stability of this solution, I noticed a glitch. Sometimes if I go into any of the test cases, it will show as if it doesn't have anything, but if you click the box, it'll show the content of the box e.g. company information, steps, or expected results in those test cases. Apart from that, I didn't see any other glitches.
I have no issues with scalability because if you want more projects, you can add more projects, and if you want more texture, spaces, or cycles, you can add them. I find it good.
Currently we don't have any technical concerns on the ALM side, so no improvement needed support-wise.
The setup was a one-time thing and I didn't find it difficult.
I was able to evaluate Jira, Confluence and Xray.
We don't have any technical concerns about the Micro Focus ALM Quality Center. Probably, it's on a different piece of Micro Focus solution called MF Connect which connects the ALM to the DevOps so that's a different one.
My advice to others looking to implement Micro Focus ALM Quality Center is that using it successfully depends on the person and the project. It may not be the same for other people, but installing it and using it offers less hassle, but I won't suggest it for everybody because analysis needs to be done when using this solution for particular projects. Users need to think about their requirements and if their requirements are not being met, then this tool may be obsolete, but as a test management stand-alone tool, it's a good tool.
I've been using this solution full-fledged and I don't see any improvements which I required in this project. I started to use this product when it was in Mercury, and Mercury then went into HP, then into Micro Focus, so I'm a longtime fan of this HPQC ALM thing. But these days, things are working differently in Agile. So Agile: It works on stories and so forth, but there is no repository of requirements or any kind of history of things. There, a project comes and it works in an Agile fashion. I don't know how good this tool is when used in an Agile perspective, but I'm sure that it is a good test management tool.
I'm rating ALM based on two points. One rating is for the product. The product is good, it's great, but when compared to other products with the latest methodologies, or when rating it as a software development tool, then I'll rate it a five out of ten because there's a lot of other great tools where you can interconnect them, use them, scale them, and leverage. It all depends on the cost.
As a stand-alone test management tool, I'm giving it a nine out of ten.
If I'm trying to scale and I'm spending more money, my rating will go down. If it's able to scale with less money like Jira, Confluence, or some other tool like Xray, then scaling may be done faster with less cost to the user.
Wherever you put five out of ten, I would say to upgrade that to seven out of ten.