When most people think of Quality Assurance—or QA to the initiated—they think of a room full of obnoxious overgrown teenagers pounding on their keyboards trying to make software malfunction. Anyone with IT experience in web application development knows there’s more to it than that, but many custom software projects run into problems because the relationship between the development team and the QA team is allowed to become too antagonistic. The developers work to make the users’ lives easier, then the QA people try to find flaws in their work. While many software vendors take a reductive approach to QA, treating it as nothing more than a search for bugs, the best approach to custom projects is to integrate QA processes into the development process from the beginning. In other words, as soon as you’re done answering the question “How should it work?” you should be going on to answer “How will we know it’s working that way?”
Continue reading What’s Most Misunderstood about Quality Assurance in Custom Software?