What do you like best?
Most valuable to us is the ability to have the system organized into distinct roles and sections. That way, we can grant different users access to the specific section they need to access. We have business users that only need to run tests, so they only need that small section of the application. We have the BA's, product trainers, who only care about the requirements.
What do you dislike?
New development methodologies, such as continuous integration and kanban boards, are being implemented by Microsoft and others to try to get their tools into the testing profession. ALM's got to push back and think more about the overall end-to-end development process. It's very much still a testing tool. We have a few awkward links rather than being a full solution.HPE ALM lacks a few of these features, but for a testing focus tool, helping to ensure quality, I think it's really good. It's good at its core necessities.
What business problems are you solving with the product? What benefits have you realized?
It has made our development process more professional. The whole interim process is a lot more professional. You can align it with the development life cycles, get the developers to buy in, and try and get it all linked in to the TFS Visual Studio.
Integration is also important to us. You've got Sprinter, which is quite nice for those that aren't familiar with what they've got to do. It's a nice little guide. Also, you can link it in with performance and automation tools, and kick things off with the push of a button