Hyuk Soo Han, Han Saem Kim

The KIPS Transactions:PartD, Vol. 13, No. 1, pp. 61-66, Feb. 2006
http://dx.doi.org/10.3745/KIPSTD.2006.13D.1.061,   PDF Download:
Keywords: Software Project Management, Rework; Inspection, Peer Review, Software Measurement, GQM
Abstract

It is reported that the success ratio of software development projects has been only 30%. Many causes lower project's chance of success, particularly lack of systematic project management. Especially, moving on the next phase of project with unsatisfactory outputs can be very problematic because it can cause much waste of resource, time and even lead to the failure of the whole project. Peer review and inspection are some of the practices designed to prevent such waste and possible failure. When defects are identified through such progress, each developer has to work on the product component again and fix the problem. This process is called rework. In this paper, we propose a method for improving quality of reworked product component to prevent excessive cost and time consumed caused by moving on the next phase of a project with a problematic product component. More specifically, this paper suggests a rework indicator that measures the level of rework based on its complexity and severity and is used to choose appropriate checking method on reworked product component. The research also confirmed the method's usefulness and effectiveness by applying the suggested method on four projects.

Statistics
Cite this article