" Keep things simple stupid.. ." The best way to answer this question would be to ask whether the Quality with which the product is being shipped is sufficient for the Customer. It goes back to our old theme - "Customer interest is paramount". Having said this, making a decision of whether the quality is sufficient from the customer perspective is a tricky one. Many issues gets raised on what is sufficient for the cusatomer and let us face it is a difficult call to make given the pressures on time to deliver and impact/side effects due to a fix. Personally, I use the process listed below to evaluate the product quality. Base Rules - QA should have the same time (if not more) as the development to test the product. Most of the time QA lags the development and hence there is a learning curve for the QA. They need to know the features first, before they can start trying to break the features. - QA should have exercised all the features of the release in an in...
- In pursuit of simplifying and clarifying Technologies related to Big Data, Social, Mobile, Analytics, Cloud and Agile.