ALM - What...why...how
Overall Satisfaction with HP Application Lifecycle Management
We utilize it in a dual function. First, we use HP Application Lifecycle Management (ALM) to monitor and control the workflow of all defects for our major custom applications. We can set up proper workflow statuses and if it is not followed, then the system notifies management of a breach in process flow which can then be followed up on. We also use it to document and track all of these defects. Second, we use it as a document repository as a replacement solution for RecPro.
Pros
- Defect management. It does a fantastic job of being able to manage the lifecycle of a defect.
- Automated testing. We use ALM in conjunction with QTP and UFT for automated tests.
Cons
- Some of the administrative functions could be better laid out. For example, you can add users to a project from within the project, but it doesn't always "take" and you have to go back to the main admin screen to add them.
- If something goes wrong with the program, it is a decent amount of work (possibly even blowing away the entire user account on the computer) in order to get it back in a working order again. This is mainly because this is a full fledged application inside of a web browser.
- Helps track defects to ensure quality of the defect (or enhancement) is met.
- Helps to make sure that the proper workflow is followed and if not, allows management to take a proactive approach to determining why the process was not followed.
We have had ALM back when it was called QC (Quality Center) and this was before my time, so I cannot say why it was chosen over other applications. I do know that it has been our defacto standard for many years now and all users of the program are very happy with it.
Comments
Please log in to join the conversation