Strategies to Reduce Rework in Software Development on an Organisation in Mauritius

Abstract

Rework is a known vicious circle in software development since it plays a central role in the generation of delays, extra costs and diverse risks introduced after software delivery. It eventually triggers a negative impact on the quality of the software developed. In order to cater the rework issue, this paper goes in depth with the notion of rework in software development as it occurs in practice by analysing a development process on an organisation in Mauritius where rework is a major issue. Meticulous strategies to reduce rework are then analysed and discussed. The paper ultimately leads to the recommendation of the best strategy that is software configuration management to reduce the rework problem in software development.

Agile Software Development – Do We Really Calculate the Costs? A Multivocal Literature Review

“…Rework can be described as redoing a process or activity that was initially implemented incorrectly, often due to changing requirements, and it can directly impact the performance and profits of an organisation, perhaps depleting 40% to 70% of a project's budget [23]. We suggest that there are genuine challenges regarding the classification of rework, especially concerning avoidable and unavoidable rework.…”

“…4) [27]. Our analysis suggests that most rework research focuses on minimizing the amount of rework in a given software project [23], and for an aspect of cost volatility as large as rework can potentially be, there was little concrete or substantial contemporary published material dedicated to measuring the cost of rework in agile settings.…”

Strategies to Reduce Rework in Software Development on IT Organization Case Study of: PT. XYZ

“…According to this paper, it stated that effective requirements management will be able to help development team of the project dramatically reduce the rework, because effective requirements management provides very clear definition of what needs to be built and makes it visible across the development team, by providing the development team with an accurate and up to date view. According to (Ramdoo, V. and Huzooree, G., 2015), in their research paper, they found that most of problem that causes a lot of rework under software development project coming out from poor communication and poor coordination between one and another in the development team. Having a low of rework in implementing software application gives significantly negative impact towards the organization such as wasting time, money, and effort of the work.…”

“…Carnegie Mellon Software Engineering Institute stated that 60-80% of the cost in software development are spent in doing a rework (Nielsen P.D.). While according to Boehm's (1987), his research shows that the cost of the rework are about 40-50% of all software development expenditure (Ramdoo, V. and Huzooree, G., 2015). In software development activity, rework becomes an unavoidable thing to do.…”

“…In software development activity, rework becomes an unavoidable thing to do. According to (Ramdoo, V. and Huzooree, G., 2015), they descried a rework in software development as an additional effort of redoing a process or activity that was incorrectly implemented in the first instance or due to changes in requirement from clients. The rework normally comes out from some problems, such as an error or failure that occurred in particular feature of the application being developed, miscommunication between the client and the development team during requirement gathering, or poor coordination between one member to other members.…”