The Pains Of Launching New Services

If you missed my 2 part Life In SCM posts you can read up if you are interested in learning about what I do as a Release Process Manager in Software Configuration Management. Where I last left off, I was discussing my role to becoming the brand awareness guy within the group. One of the things I love doing is taking feedback/enhancement requests and implementing them for the user. One of those things was providing a better interface for our developers and project leads to interact with. This interface allows them to view their development builds running in real time and allows them on-demand access to execute the builds when they need them. They also receive trending reports, test results, and more.

Life In SCM PT.1

scmI figured I would write a little bit more about what I do for work. I am a software configuration guy. Meaning I track changes to the code, build code, manage release process, and maintain environment. Let’s start with my entry into SCM…

At my previous company I began to administrate and develop for the Remedy system. We tracked all changes in IT with this system, and I produced all the reporting, and tool for submitting change requests. I also began to run one of our change control meetings for the desktop group. I was then thrown into change control. While performing my new duties I wondered on several occasion’s on how this development team can code something, release to prod (internal app that produced material for clients), and not have anyone test. Not only that but they would throw a fit if you contacted them about some bug or failure? Change control that really isn’t controlled, huh.