Mission-Critical Development With XP & Agile Processes: Common code ownership and lots of testing
Our system, which was developed over a period of several years, was a spaghetti-like system that consisted of C-based applications and scripts and had grown into an unmanageable piece of software that was difficult to improve and maintain. Finally, it became clear that a new, more generic and extensible system was needed: Management decided that replacement was in order. Furthermore, it was decided that a new system would be implemented using Java. At the outset, we decided to base our development process on Extreme Programming and adopt agile practices for our daily work. In this article, I describe those practices, starting with the development process itself, then focus on the two practices that proved the most valuable.
Author: Julius Gawlas
Published: Dr. Dobbs’s Journal, January 2004
link
