Such is the case that if the defects are transferred all the way to the final acceptance testing phase of the project life cycle, the greater risk of time consumption and costing increases. Consequently, small effort advanced towards quality assurance will help reduce expenses to a greater degree with regard to detecting and rectifying the defects.
To better understand the effectiveness of the processes of agile software. it is important to gather facts on defects identified in the previous projects and also examine how the same defects can be eliminated following process improvements and application of newer methodologies. This paper presents comprehensive view on the defect prevention techniques and practices that can be followed in agile software development. In handling this topic the paper will look into related work and further discusses the need for defect deterrence. Additionally, the work will address handle issues of improvement workflow along with the illustration of various stages, the root cause analysis and determination of precautionary action.
Agile software defect simply refers to “Imperfections in agile software development process that would cause agile software to fail to meet the desired expectations”. During the long and complex process of agile software development, lot of defects frequently occurs. One misleading notion is that defects crop into the process at the start of the cycle and is eliminated all through the remaining development phases. The truth is that defects form part of the development process from the very beginning to the end, a factor that makes its prevention an essential part in the agile software process quality improvement.
Defect prevention (DP) refers to quality improvement process whose aim is to discover regular causes of defects and prevent their reoccurrence through alteration of the relevant process (es).