Thomas Carlier is a Continuous Integration Engineer with 20 years in the computer industry; specializing for the last 15 years in the build engineering and software configuration management arena. Currently a Senior DevOps Engineer at Tripwire, Inc., Thomas has previous experience with large and small R&D organizations, including Informix Software, IBM, and Kryptiq.
He has a passion for understanding the growing pains of successful software development organizations, He believes the seemingly uncontrollable, and often chaotic transitions from startups to enterprise organizations can be tamed into a simple [but not easy] disciplined and somewhat controlled set of processes if we plan for change when we design our SCM and other SDLC procedures.
Thomas holds a Bachelor or Science degree in Business Computer Information Systems from St. Cloud State University and is a graduate of the Oregon Masters of Software Engineering program at Portland State University.
All content posted to this website represent the viewpoints of the author and are not sponsored by any current or past employers.
The acronym “SCM” is also expanded as source configuration management process and software change and configuration management .
Very true. Another use of the SCM acronym that has coming into play is “security configuration management.”
And one that has been around for some time; Supply Chain Management. There are just too many acronyms out there, which is why IBM (which is in itself a 3 letter acronym) developed an internal acronym dictionary.