Application Lifecycle Management and Application Transformation Blog
Sharing HP’s point of view on Application Lifecycle Management, sharing customer best practices and advice on managing the lifecycle of applications from concept to retirement.

Live from Israel-ALM Best Practices: Change is good, but the familiar is even better



שלום (Shalom) again from Israel!  The R&D teams have renamed our little think tank “קהל קשה” (meaning hard audience or tough crowd). All of our questions start with “I have customer that has this problem and what has R&D done to address it?” We sound like personal lobbyists always pushing our pet projects. In all honesty, the R&D team had answers to almost all of our questions and the other questions were well documented  and assigned to the group for further study. We all know that nothing is perfect, but with R&D’s Agile style of shorter intervals between updates and patch, I think the user community will be happy.


Israel Beach.pngOn Day two we looked at adding all the new functionality with best practices in the new version of HP Application Lifecycle Management (ALM).  Our focus was on helping our customers adopt this functionality while making sure they won’t face a steep learning curve. I am happy to say I believe customers will find this new version refreshing.  


We started the third day reviewing the installation documents while discussing typical install issues. One of the main topics was the importance of making sure our customers can find the KM documents for install without having to call support. Success is measured in how simple it is for a user to find the information they need. We also discussed how important it is to remember that installing ALM is a very small part of the install and upgrade process. We need to support the complete upgrade process.


In the afternoon we started talking about the business need for reporting. It is vital that users be able to draw the information out of ALM without having to create complex SQL statements. You want them to execute directly from the database and work after every patch. The best practice is that the data comes off the database directly and each user utilizes the internal tools—no more manual creation of these reports!  


Next up was memory analysis and performance, which make trouble shooting so much easier. This includes enhancements in the active security as well as passive for tracking and monitoring. We also swapped war stories.


If you have question about best practices I recommend contacting your support agent or you can always post the question in the comments section of this blog. In addition, stay tuned for more information about the newest version of ALM and details about all the new features it offers here at the ALM blog or on the ALM homepage.


Leave a Comment

We encourage you to share your comments on this post. Comments are moderated and will be reviewed
and posted as promptly as possible during regular business hours

To ensure your comment is published, be sure to follow the Community Guidelines.

Be sure to enter a unique name. You can't reuse a name that's already in use.
Be sure to enter a unique email address. You can't reuse an email address that's already in use.
Type the characters you see in the picture above.Type the words you hear.
Showing results for 
Search instead for 
Do you mean 
About the Author
Michael Deady is a Pr. Consultant & Solution Architect for HP Professional Service and HP's ALM Evangelist for IT Experts Community. He spec...

Follow Us
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.