For every working version of a software application, there are usually many other copies of it running that are broken or being tested.
Changes in software percolate their way up through a minefield of development and testing, until they reach the point where they are ready to be released. Having a streamlined process in place to handle this has been proven to save money, time and a great deal of frustration.
Release Management doesn’t get a lot of press: probably because it’s very technical and dull as the dickens. That said, we’ve bored ourselves to death with it, so you don’t have to.
Our pain was your gain. Over the years, we’ve developed a very reliable system for managing changes in our development food chain, which means that some of the ugliest byproducts of poor release management are unlikely to ever see the light of day in what we build for you.
What kind of ugly things, you might ask? Here are a few nasties:
- Bugs that got fixed in the past suddenly reappearing in a new release.
- Rarely used parts of a system suddenly breaking because some module was accidentally left out when the system was released.
- New bugs appearing because the wrong version of a 3rd party component was included in a release.
- Someone forgot to type in some configuration information somewhere, so something broke and you’ll have to take your system offline to fix it.
The list goes on, but we’re not into fear-mongering… and hey, it was hard enough to read those 4 things without falling asleep.
We just want you to know that Release Management is a black art that we’ve got a good grasp on. We’d love to apply what we know to your software project, but we’re also available to consult with you to help you create a reliable Release Management process, if that’s one of your sore spots.
For more information about how we can save you time, money and/or frustration by way of a solid Release Management process, please contact us.