How do you know the software product your team produces is quality? Well the answer is… you don't really know, the only people that can evaluate the quality of a piece of software is the customer. Some of you may disagree, but for me having been part teams that develop software that we don’t use on an everyday basis in real world situations, we are not in a position to say whether it is quality or not. It's like building a car and never driving it - how do you know it's any good? However, what we can do is understand under what conditions we are happy to ship our product to our clients. What we can do is to define what we think our 'internal quality' is and what it looks like. So how can we define what quality looks like? In the dim and distant past I have worked in places where so long as the software worked it was OK to be shipped. Yeah they may have been a quick check to make sure the system wasn’t slow but outside of that it was pretty much all about fu