Extreme Programming With Legacy Code

Are there any considerations to take when implementing XP on projects already underway? What about systems already running in a production environment? Should test-code-refactor be done any different?

Egroups:

Articles: Books:


My PhD thesis was primarily about legacy systems: what they are, how they got that way, how to deal with them, and how to stop them from happening again. The main thrust of it combines a lot of the lessons from XP and other agile methodologies (particularly Scrum and Crystal).

Although it was awarded by a university, in large part it is actually based on work on some real systems in industry (with an industrial partner company).

I have just got around to putting it on the Web (it was awarded in August 2001, so I have been a bit slow!):

[broken links removed]

If you do read it, I would be very interested in your thoughts.

-- AnthonyLauder


See: ExtremeProgrammingImplementationIssues, UnitTestingLegacyCode, UnitTest, RefactoringLegacyCode, AddingFeaturesToLegacyCode, LegacyCode

CategoryExtremeProgramming


EditText of this page (last edited August 1, 2014) or FindPage with title or text search