You Need a Change Control Process for your Software Projects

Protect your systems from human error with a few simple steps

Image for post
Image for post
Don’t let this be you! Photo by Stephen Radford on Unsplash

Change Control is Good

Change control “reduces the possibility that unnecessary changes will be introduced to a system without forethought, introducing faults into the system or undoing changes made by other users of software.” Taking a moment to think through how your change can affect existing systems is a vitally important part of software development.

The One Thing You Have to Do

Impact analysis is the one thing that needs to be a part of every change control action. No matter how monumental or insignificant you think your change is, you need to take a step back and look at what it could potentially do to your production systems.

What’s Your Backout Plan?

Image for post
Image for post
Photo by Hush Naidoo on Unsplash

Write it All Down

Ah, documentation. The bane of all software engineers.

Another Set of Eyes

One of the most important reasons you need to write it all down is so you can give your plan and analysis to another engineer to look at.

No More Blowing Things Up

Having a change control process (with associated documentation) can keep you from blowing things up. Businesses don’t like their smooth, profit-making machines out of operation, and developers don’t like doing extra work cleaning up messes.

Technology professional in Hollywood, so naturally I also make terrible short films and tech videos.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store