http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660"my own definition for legacy code is "code that makes money". As such, any modifications to it should be justified in terms of ROI." Well said. http://ayende.com/3649/it-might-work-but-is-it-good-enough#comment4http://ayende.com/3649/it-might-work-but-is-it-good-enough#comment4Wed, 15 Oct 2008 18:04:45 GMTThe way we handle this on our agile project is to avoid refactoring certain areas until a change request comes in around that area. We then increase the estimate to give us time to perform the refactoring. This can increase a simple 1 day change to 5 days, but we explain the reason it will take so long is because we need to refactor certain areas of the system first in order to accomodate this change. Of course we are lucky that the system was originally developed by someone else as we can blame them for the "bad design" we have inherited ;-) http://ayende.com/3649/it-might-work-but-is-it-good-enough#comment3http://ayende.com/3649/it-might-work-but-is-it-good-enough#comment3Wed, 15 Oct 2008 13:26:32 GMTThat's funny, especially because NDepends concept of instability is quite something else than how business people understand it. Next time I work for meat industry, I am sure going to implement something "bleeding edge" there :), they are bound to like it. http://ayende.com/3649/it-might-work-but-is-it-good-enough#comment2http://ayende.com/3649/it-might-work-but-is-it-good-enough#comment2Wed, 15 Oct 2008 12:12:08 GMTI had the same problem convincing business people that we needed to refactor. Turns out that showing them an output from running Ndepends on our code and in particular the word "Instability" shoved them in the right direction. http://ayende.com/3649/it-might-work-but-is-it-good-enough#comment1http://ayende.com/3649/it-might-work-but-is-it-good-enough#comment1Wed, 15 Oct 2008 07:28:40 GMT