Product Quality Testing Essay Example | Topics and Well Written Essays - 1500 words

Product Quality Testing - Essay Example The big question here is how much testing needs to be done, because the testing requires time, which is precious because the clients and users want the product as soon as possible. The paper will include sources that will be used in order to support the question of how much testing needs to be done in order to ensure a good quality product and to show that there is a problem when too much or too little testing is done. A review of literature will be presented to show how we come up with the conclusion. The review includes the study done by Rothman (2001) on release criteria. Rothman (2001) tackles when to release a software/ Also in the article written by Barbara Tallent (2008) she discusses when it is enough for testing and releases it in market. At the end of the paper a conclusion was given and the paper will try to find the best answer on the addressed question. In the article written by Johanna Rothman (2001) "Release Criteria: Defining the Rules of the Product Release Game," he discusses the problems involve in releasing the product early. He also point out that the decision of releasing the product comes from the higher authority of the organization usually the production managers. The article includes the case of Rita who heads the team in developing software. The production manager is being pressured by the customers and needs to release the product as soon as possible. In order to do so Rita and PM releases criteria for the team to decide. The criterion includes; All code must compile and build for all platforms Zero high priority bugs For all open bugs, documentation in release notes with workarounds All planned QA tests run, at least 90 percent pass. Number of open defects decreasing for the last three weeks. Feature x unit tested by developers, system tested by QA, verified with customers A, B before release. All open defects evaluated by cross-functional team. The decision in releasing the product at earlier time should comply with the release criteria. The release criteria objectives are specific, measurable, attainable, relevant, and trackable. Before releasing the product it should agreed upon by the entire project team and understood by senior management. The reasons for such release should be reasonable enough. Rothman (2001) in the article uses the release criteria to evaluate whether the product can be release or not. This also assesses the entire project and the prediction of an early warning on the incoming problem on the product. Based on the article a product can be released as long as it complies with the release criteria created by the team. Another review on the immature release of the product is shown in the article written by Bernadette Tallent (2008). In this article she presented a case study wherein the VP of marketing for a software company was about to release a new product. The product was incomplete and the team knows it. Extensive user testing on the product has been done and they concluded that the product was missing several key features. Meetings have been done to assess whether or not to release the product in the market. In order to decide in releasing or not releasing the product the group listed trade offs: Reasons to Release The product was stable The product was due to be announced at an Internet World - if we missed the release date we would miss the