Refactoring as a Lifeline: Lessons Learned from Refactoring

Abstract

Refactoring legacy code can be a major impediment for teams transforming to agile due to the high cost of manual regression testing of frequent (typically 2-week) releases. Also, attempts to implement automated tests may involve technical and cost issues. In this report we present a new and more systematic approach to refactoring we have found to be successful for refactoring legacy code that has few (if any) automated tests. This report describes two experiences: one with 3 teams applying a basic and traditional refactoring approach, and another with 2 teams applying the new approach. This new approach helped achieve better results in covering code with tests, involved senior management to retain their support, and achieved better and more sustainable pace of development powered by continuous refactoring techniques.