As a life-long learner and practitioner, I taught myself many skills and techniques. In application to my job, I take on anything needed and figure it out.
The particular project I once had was to establish a structured Issue Management process in my Client company, utilizing HP ALM QC tool.
I approached it and carried out with the following steps.
1. Learn about current processes, per project. Identify purposes and key steps. Understand interaction model – roles and responsibilities with regards to the issue management. Understand and document state transitioning and metrics.
2. Review the existing processes with the whole QA team and management. Facilitate definition of a unified structured model. Create a document to use as an operational guide.
3. Configure HP ALM tool according to the model defined.
(Of course, it’s not over after the step 3. Roll-out, training, and support steps are besides the scope of this blog entry as I’m focusing on the technical part.)
Step 3 – HP ALM Quality Center customization was a technical process I’ve never done before. It became a little project in itself – explore customization capabilities, experiment with the code and configuration, implement VBScripts, test the solution.
This kind of hands-on learning is cemented with note-taking and summarizing of experiences. I’ve used my blog for this purpose, sharing business-agnostic examples when possible.
All the content referenced below does not copy or represent a commercial solution. This is a collection of ideas and implemented concepts, research and investigations results. If you use it, you use it at your own risk.
Unauthorized use and/or duplication of materials from this blog without express and written permission from this blog’s author and owner is strictly prohibited. Excerpts and links may be used, provided that full and clear credit is given to Albert Gareev with appropriate and specific direction to the original content.
Unless otherwise stated, all code examples, functions, function libraries, workarounds, etc. are created by Albert Gareev, and are copyrighted.
You may use them to design, develop and test your own software. You may modify the original source code as you need.
However, you must ensure that full and clear credit is given to Albert Gareev with an appropriate and specific direction to the original content. If your Employer’s policies restrict that then you may not use the source code provided.