Daily updates keep rolling in and all indicate that our Early Evaluation Program (EEP) for myCMDB continues to progress nicely. We have been contacted numerous times by both customers and internal employees with feature suggestions, questions and bug reports. A handful of folks with whom we have never spoken with previously have even sent inbound requests to give the software a try.
In many ways, the EEP has also become an extension to our QA department. Many people find that it is fun to find a bug and to report these to us. While we don’t necessarily “like” having to fix these bugs since we would rather be working on features -- we know this is a vital part of the process and are very happy to find them early in the development process where the overall cost to fix is dramatically lower.
We have been following standard practice by categorizing the enhancement requests and bugs and placing them into our ticketing system so that they can be reviewed and addressed by the proper personnel during the proper time in the schedule. We are working to manage these fixes in between preparation for our next “formal” code drop for the EEP. We have been updating the code periodically during our maintenance periods for a few fixes we deem necessary, however, we are not delivering additional major features to the product until our next code drop in August.
Currently we are aggregating overall usage data and it will be interesting to see if there are significant trends: What type of user logs in most frequently? Who uses it less frequently? Who is leveraging the community aspects? Are the CIM standard for CI’s useful or have they constructed their own classes? Stay tuned.
- Adam
Leave a comment