Software Build and Release Specialist

An SCM group just isn’t serious without proper vision statements and lofty goals. Even if you’re the lone SCM Engineer within your group, you should still strife for certain milestones.  The software field is constantly evolving which means SCM should closely mirror that evolution.

It should be the ultimate goal of an SCM Engineer to automate him/herself out of a job.  This may not make sense to some of you, but when you think about it–it should make perfect sense.  Our specialties are to enforce, streamline, and automate all software development activities. Forget the notion of ‘job security‘ by holding on to a certain build process that ONLY you know how to perform because at the end, it will only be detrimental to your career.

By sharing, automating, cross-training, and documenting all the processes, tools, and activities within the SCM group; you free yourself from a lot of manual tasks and at the same time, you become a leading edge industry expert within your field because you’ve worked with the latest and greatest.

This is my vision statement or somewhat of a professional credo, so to speak:

SCM is the singular working entity within [insert org name] that is responsible for planning, designing, defining, implementing, and managerial duties of the SCM build and release infrastructure, hardware and software architecture, processes, and activities by which to support the life-cycle of any Software Development Group/Project/Process.

Now, what’s yours?