If you’ve been reading our content about the importance of processes, you know the kinds of things that happen when standard procedure isn’t followed. Satellites crash, nuclear reactors melt down, and information security disasters ruin huge corporations.
For software companies, failure doesn’t always have such wide implications but it can mean carelessly shipping a product that creates catastrophic problems for your customers and destroys their trust in you. And of course, it’s a pain in the arse for your development team to fix.
In this article, I’m going to go over some famous software disasters where Quality Control dropped the ball, and look over some common quality control methods.