Executive Summary- summary report purpose and findings and Revision history Table of Contents Introduction- motivation for report and description of structure As a software quality manager for this company, I aim to ensure our website is to a very high standard, meeting all uptime targets as well as delivering a high standard of customer satisfaction. The main aim of this report is to provide you (the board of directors) the findings of my research as to which methodology we as a company should adapt to, in order to not only keep on top of our targets, but to exceed them, as well as delivering a higher customer satisfaction as a result of our website. Part 1- Software Quality and Agile Methods There are many strengths and weaknesses related …show more content…
This can be through senior bodies within a company, as well as customers who provide feedback through various methods such as user testing or forums on websites. The feedback given by either the customer or senior bodies within the company allow changes to be implemented within the requirements aiding in the improvement of the product being created in terms of its quality. The feedback received reflects the feelings of the customer and after implementing the changes from the feedback received can help increase customer satisfaction. The changes in requirements are always customer focused within agile, as the purpose is to increase customer satisfaction. Gathering results from both senior bodies within the business as well as the customers feedback, can allow more extensive testing in order to improve the quality of the product being created. Customer Involvement As the customer is actively involved throughout the project, their feedback throughout the project aids in the planning, developing, and implementing stages of the project, and the product itself is created in a way that increases the satisfaction of the customer as well as improving the reputation of the business …show more content…
In addition to this, as they conduct tests and gain reviews throughout the process, as well as producing frequent builds during each iteration, the quality of the product is improved, as defects are found and fixed quickly. In addition to this code is refactored during the development process, which leads to code being removed as well as reused, improving the overall quality. With the application of refactoring, this can also improve the quality of design as well as performance of the product. Sprint retrospectives allow the team as a whole to reflect on the work conducted during a sprint, this enables the team to collectively discuss what they can improve, as well as provide ideas amongst the team in order to incorporate these ideas into future sprints, allowing the improvement in the quality of a