Each and every software defect adds unplanned work—essentially rework—to the schedule. IT must tackle rework head on to determine the most appropriate areas for improvement, investment, and increased quality.
This report provides cost of rework models for Agile and non-Agile projects and recommends ways to test earlier to reduce rework and its cost. Learn how to reduce the cost of rework in development and testing to help prevent catastrophic defects from occurring in production.
Research subscribers, please login to access this report. Subscribe now to access this report or purchase on-demand access.
The concept of the Cost of Quality, that is, the cost of rework to remove defects, is that the later in the lifecycle a defect is identified, the more expensive it is to resolve the issue. With its shift in requirements ownership from the business to developers who will discover requirements through changes to the source code, the Agile movement is effectively pushing requirements definition to later in the lifecycle. Applying models for the cost of rework to Agile projects reveals the hidden costs of the late definition of requirements. This report provides economic models for evaluating project results and selecting the most appropriate practices.
This report is available to voke's premium research subscribers and on-demand.
