Abstract
Many information systems development companies are facing the question on how to apply agile methods in information systems maintenance (ISM). Performing correction of software defects in ISM inevitably degenerates program structure. On the other hand, agile methods provide refactoring to improve program structure without changing its behavior. This paper builds an optimal control model to balance the trade-off between defect correction and refactoring. We answer three questions. First, is that optimal to perform parallel defect correction and refactoring? Second, how to determine the iteration length for agile ISM if team wants to include refactoring in the iteration? Third, how long the iteration should be if team wants to improve program’s structure to a certain level at the end of the iteration? To our knowledge, this paper is the pioneer in understanding agile ISM policy analytically. Managerial implications of the results are also discussed in the paper.
Recommended Citation
Ren, Jimmy; Wang, Wei; Hua, Zhimin; Xu, Kaiquan; and Liao, Stephen, "Optimal Refactoring Policy for Agile Information Systems Maintenance: A Control Theoretic Approach" (2011). ICIS 2011 Proceedings. 5.
https://aisel.aisnet.org/icis2011/proceedings/projmanagement/5
Optimal Refactoring Policy for Agile Information Systems Maintenance: A Control Theoretic Approach
Many information systems development companies are facing the question on how to apply agile methods in information systems maintenance (ISM). Performing correction of software defects in ISM inevitably degenerates program structure. On the other hand, agile methods provide refactoring to improve program structure without changing its behavior. This paper builds an optimal control model to balance the trade-off between defect correction and refactoring. We answer three questions. First, is that optimal to perform parallel defect correction and refactoring? Second, how to determine the iteration length for agile ISM if team wants to include refactoring in the iteration? Third, how long the iteration should be if team wants to improve program’s structure to a certain level at the end of the iteration? To our knowledge, this paper is the pioneer in understanding agile ISM policy analytically. Managerial implications of the results are also discussed in the paper.