Abstract
Extreme programming (XP) is an agile software process that promotes early and quick production of working code. In this paper, we investigated the relationship among three XP engineering activities: new design, refactoring, and error fix. We found that the more the new design performed to the system the less refactoring and error fix were performed. However, the refactoring and error fix efforts did not seem to be related. We also found that the error fix effort is related to number of days spent on each story, while new design is not. The relationship between the refactoring effort and number of days spent on each story was not conclusive.
| Original language | English |
|---|---|
| Pages (from-to) | 1068-1072 |
| Number of pages | 5 |
| Journal | Information and Software Technology |
| Volume | 48 |
| Issue number | 11 |
| DOIs | |
| State | Published - Nov 2006 |
Bibliographical note
Funding Information:The authors would like to thank the anonymous reviewers for their constructive contributions. The author also acknowledge the support of King Fahd University of Petroleum and Minerals in the development of this work.
Keywords
- Design evolution
- Empirical study
- Extreme programming
- Extreme programming engineering activities
ASJC Scopus subject areas
- Software
- Information Systems
- Computer Science Applications